Google Container Analysis: Node.js Client

release levelnpm version

Containeranalysis client for Node.js

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

Read more about the client libraries for Cloud APIs, including the olderGoogle APIs Client Libraries, inClient 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 theAPI from your local workstation.

Installing the client library

npm install @google-cloud/containeranalysis

Samples

Samples are in thesamples/ directory. Each sample'sREADME.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.export_s_b_o_msource 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

TheGoogle Container Analysis Node.js Client API Reference documentationalso contains samples.

Supported Node.js Versions

Our client libraries follow theNode.js release schedule.Libraries are compatible with all currentactive andmaintenance versions ofNode.js.If you are using an end-of-life version of Node.js, we recommend that you updateas soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on abest-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, andcan be installed through npmdist-tags.The dist-tags follow the naming conventionlegacy-(version).For example,npm install @google-cloud/containeranalysis@legacy-8 installs client librariesfor versions compatible with Node.js 8.

Versioning

This library followsSemantic Versioning.

This library is considered to bestable. The code surface will not change in backwards-incompatible waysunless absolutely necessary (e.g. because of critical security issues) or withan extensive deprecation period. Issues and requests againststable librariesare addressed with the highest priority.

More Information:Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See theContributing Guide.

Please note that thisREADME.md, thesamples/README.md,and a variety of configuration files in this repository (including.nycrc andtsconfig.json)are generated from a central template. To edit one of these files, make an editto its templates indirectory.

License

Apache Version 2.0

SeeLICENSE

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-10-30 UTC.