@google-cloud/profiler
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): ms and @google-cloud/promisify are well-established packages; swap from parse-duration is a routine dependency update. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Google-maintained package published via trusted vendor bot; inactivity gaps are normal for stable infrastructure libraries. | ai | |
| phantom-deps | phantom-dep:teeny-request | AI (phantom-deps): HTTP transport dep used transitively; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:protobufjs | AI (phantom-deps): Declared as runtime dep for proto serialization; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/console-log-level | AI (phantom-deps): Type-only package; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@google-cloud/promisify | AI (phantom-deps): Google Cloud utility dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type-only package; framework-scoped, not directly imported at runtime. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 6.0.4 | 15 / 24 | |
| 6.0.3 | 15 / 23 | |
| 6.0.2 | 14 / 22 | |
| 6.0.0 | 14 / 22 |
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.