← Home

googleapis

npm Repository Homepage
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

google-wombot

Keywords

googleapigoogle apisclientclient library

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:build/src/apis/policytroubleshooter/v3.d.ts AI (source-diff): Auto-generated TypeScript declaration file for Google API surface; long lines are from machine-generated type definitions, not obfuscation. ai
source-diff obfuscated-file:build/src/apis/policytroubleshooter/v3beta.d.ts AI (source-diff): Auto-generated TypeScript declaration file for Google API surface; long lines are from machine-generated type definitions, not obfuscation. ai
publish-pattern dormant-publish AI (publish-pattern): googleapis is actively maintained with 289 versions; publisher google-wombot is a known Google automation account. ai

Versions (showing 12 of 12)

Version Deps Published
171.4.0 2 / 40
171.3.0 2 / 40
171.2.0 2 / 40
171.1.0 2 / 40
171.0.0 2 / 40
170.1.0 2 / 40
170.0.0 2 / 40
169.0.0 2 / 40
168.0.0 2 / 40
167.0.0 2 / 40
166.0.0 2 / 40
165.0.0 2 / 40

v171.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v171.3.0

3 findings
HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3beta.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v171.2.0

3 findings
HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3beta.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v171.1.0

3 findings
HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3beta.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v171.0.0

3 findings
HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: build/src/apis/policytroubleshooter/v3beta.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v170.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v170.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v169.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v168.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v167.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v166.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v165.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.