@balena/node-metrics-gatherer
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): TypeScript type package; correctly declared for type support in dependencies. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): TypeScript type package; correctly declared for type support in dependencies. | ai | |
| phantom-deps | phantom-dep:@types/on-finished | AI (phantom-deps): TypeScript type package; correctly declared for type support in dependencies. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.1.2 | 8 / 11 | |
| 6.1.1 | 8 / 11 | |
| 6.1.0 | 8 / 11 | |
| 6.0.5 | 8 / 11 | |
| 6.0.4 | 8 / 11 |
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.