@google-cloud/nodejs-repo-tools
Tools used to maintain and test Node.js repositories in the GoogleCloudPlaftorm organization.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal is expected: jdobry maintains many Google Cloud Node.js tooling packages with templated names. This is a legitimate Google Cloud developer tool, not spam. | ai | |
| phantom-deps | phantom-dep:semistandard | AI (phantom-deps): semistandard is a linting tool referenced in package.json config; phantom-dep pattern is normal for dev tools. | ai | |
| dependencies | unvetted-dep:string | AI (dependencies): [email protected] is a well-known utility library pinned to a specific version; no advisory flagged. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): [email protected] is a well-known templating library; no OSV advisory flagged for this version in this context. Stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): semver is a canonical, widely-trusted npm package; its addition to a Google Cloud build tooling package is benign and expected. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawning processes is the primary purpose of this repo-tools CLI; not malicious. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): exec() used in runAsync helper for developer tooling; expected and documented behavior for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in build_pack.js is used to load build pack configuration files — a legitimate plugin/config loading pattern for this tooling package. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): google-wombot is Google's official automation account for GCP Node.js packages; the transition from google-node-team to google-wombot is a documented Google-wide publishing migration, not a hijack. | ai | |
| phantom-deps | phantom-dep:nyc | AI (phantom-deps): nyc is declared in dependencies and used in config sections; phantom-dep finding is a false positive. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2019, predating Sigstore provenance availability; not a meaningful risk signal for this era. | ai | |
| phantom-deps | phantom-dep:ava | AI (phantom-deps): ava is declared in dependencies and used in config sections; phantom-dep finding is a false positive. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): google-wombot is Google's official bot account; addition is part of Google's automated publishing migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual Google maintainers in favor of google-wombot bot is consistent with Google's GCP Node.js publishing automation migration. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from google-node-team to google-wombot reflects Google's migration to automated publishing; not an account compromise. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): This is a CLI/developer tooling package that explicitly runs test commands and system processes; child_process usage is core expected functionality. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 14 / 8 | |
| 2.3.3 | 14 / 8 | |
| 2.3.0 | 14 / 8 | |
| 2.2.0 | 13 / 8 | |
| 2.0.9 | 13 / 3 | |
| 2.0.8 | 13 / 3 | |
| 2.0.7 | 13 / 3 | |
| 1.4.17 | 11 / 0 | |
| 1.4.16 | 11 / 0 | |
| 1.4.15 | 11 / 0 | |
| 1.4.14 | 11 / 0 | |
| 1.4.13 | 11 / 0 | |
| 1.4.12 | 11 / 0 | |
| 1.4.11 | 11 / 0 | |
| 1.4.10 | 11 / 0 | |
| 1.4.9 | 11 / 0 | |
| 1.4.8 | 11 / 0 | |
| 1.4.7 | 11 / 0 | |
| 1.4.6 | 11 / 0 | |
| 1.4.5 | 11 / 0 | |
| 1.4.4 | 11 / 0 | |
| 1.4.3 | 11 / 0 | |
| 1.4.2 | 11 / 0 | |
| 1.4.1 | 11 / 0 | |
| 1.4.0 | 11 / 0 | |
| 1.3.5 | 13 / 0 | |
| 1.3.4 | 13 / 0 | |
| 1.3.3 | 13 / 0 | |
| 1.3.2 | 13 / 0 | |
| 1.3.1 | 13 / 0 | |
| 1.3.0 | 13 / 0 | |
| 1.2.1 | 13 / 1 | |
| 1.2.0 | 13 / 1 | |
| 1.1.11 | 13 / 1 | |
| 1.1.10 | 13 / 1 | |
| 1.1.9 | 13 / 1 | |
| 1.1.8 | 13 / 1 | |
| 1.1.7 | 13 / 1 | |
| 1.1.6 | 13 / 1 | |
| 1.1.5 | 13 / 1 | |
| 1.1.4 | 13 / 1 | |
| 1.1.3 | 13 / 1 | |
| 1.1.2 | 13 / 1 | |
| 1.1.1 | 13 / 1 | |
| 1.1.0 | 13 / 1 | |
| 1.0.8 | 4 / 1 | |
| 1.0.7 | 4 / 1 | |
| 1.0.6 | 4 / 1 | |
| 1.0.5 | 4 / 1 | |
| 1.0.4 | 4 / 1 | |
| 1.0.3 | 4 / 1 | |
| 1.0.2 | 4 / 1 | |
| 1.0.1 | 4 / 1 | |
| 1.0.0 | 4 / 1 |
v3.3.0
3 findingsAll previous maintainers (fenster, google-node-team, justinbeckwith, ofrobots) were replaced by new maintainers (google-wombot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2019-05-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-27. This could indicate a legitimate maintainer transition or an account compromise.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.