Google Container Analysis: Node.js Client

release level npm version

Containeranalysis client for Node.js

A comprehensive list of changes in each version may be found in the CHANGELOG.

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:

Quickstart

Before you begin

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Google Container Analysis API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/containeranalysis

Samples

Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

SampleSource CodeTry it
Container_analysis.get_iam_policysource codeOpen in Cloud Shell
Container_analysis.get_vulnerability_occurrences_summarysource codeOpen in Cloud Shell
Container_analysis.set_iam_policysource codeOpen in Cloud Shell
Container_analysis.test_iam_permissionssource codeOpen in Cloud Shell
Grafeas.batch_create_notessource codeOpen in Cloud Shell
Grafeas.batch_create_occurrencessource codeOpen in Cloud Shell
Grafeas.create_notesource codeOpen in Cloud Shell
Grafeas.create_occurrencesource codeOpen in Cloud Shell
Grafeas.delete_notesource codeOpen in Cloud Shell
Grafeas.delete_occurrencesource codeOpen in Cloud Shell
Grafeas.get_notesource codeOpen in Cloud Shell
Grafeas.get_occurrencesource codeOpen in Cloud Shell
Grafeas.get_occurrence_notesource codeOpen in Cloud Shell
Grafeas.list_note_occurrencessource codeOpen in Cloud Shell
Grafeas.list_notessource codeOpen in Cloud Shell
Grafeas.list_occurrencessource codeOpen in Cloud Shell
Grafeas.update_notesource codeOpen in Cloud Shell
Grafeas.update_occurrencesource codeOpen in Cloud Shell
Container_analysis_v1_beta1.generate_packages_summarysource codeOpen in Cloud Shell
Container_analysis_v1_beta1.get_iam_policysource codeOpen in Cloud Shell
Container_analysis_v1_beta1.get_scan_configsource codeOpen in Cloud Shell
Container_analysis_v1_beta1.list_scan_configssource codeOpen in Cloud Shell
Container_analysis_v1_beta1.set_iam_policysource codeOpen in Cloud Shell
Container_analysis_v1_beta1.test_iam_permissionssource codeOpen in Cloud Shell
Container_analysis_v1_beta1.update_scan_configsource codeOpen in Cloud Shell
Grafeas_v1_beta1.batch_create_notessource codeOpen in Cloud Shell
Grafeas_v1_beta1.batch_create_occurrencessource codeOpen in Cloud Shell
Grafeas_v1_beta1.create_notesource codeOpen in Cloud Shell
Grafeas_v1_beta1.create_occurrencesource codeOpen in Cloud Shell
Grafeas_v1_beta1.delete_notesource codeOpen in Cloud Shell
Grafeas_v1_beta1.delete_occurrencesource codeOpen in Cloud Shell
Grafeas_v1_beta1.get_notesource codeOpen in Cloud Shell
Grafeas_v1_beta1.get_occurrencesource codeOpen in Cloud Shell
Grafeas_v1_beta1.get_occurrence_notesource codeOpen in Cloud Shell
Grafeas_v1_beta1.get_vulnerability_occurrences_summarysource codeOpen in Cloud Shell
Grafeas_v1_beta1.list_note_occurrencessource codeOpen in Cloud Shell
Grafeas_v1_beta1.list_notessource codeOpen in Cloud Shell
Grafeas_v1_beta1.list_occurrencessource codeOpen in Cloud Shell
Grafeas_v1_beta1.update_notesource codeOpen in Cloud Shell
Grafeas_v1_beta1.update_occurrencesource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell
Quickstart.testsource codeOpen in Cloud Shell

The Google Container Analysis Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:

  • Legacy versions are not tested in continuous integration.
  • Some security patches and features cannot be backported.
  • Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/containeranalysis@legacy-8 installs client libraries for versions compatible with Node.js 8.

Versioning

This library follows Semantic Versioning.

This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.

License

Apache Version 2.0

See LICENSE