google-ads-node
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
axelvermeilcn-dopteobotjcamero92digi-commilos_optepmaxime_opteolewis_opteofidelopteokritzware
Keywords
google ads apigoogle adsgoogle ads nodejsgoogle ads jsads nodegrpcproto
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): lru-cache is a well-known utility likely used transitively via google-gax; stable false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 23.0.0 | 2 / 2 |
v23.0.0
2 findings
HIGH
Phantom dependency: lru-cache
phantom-deps
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
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.