@metrics/client
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Long-persisted publisher change with no takedown; already vetted in prior versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same historical maintainer transition, no new change this version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy predates this version; diff shows no material changes. | ai | |
| phantom-deps | phantom-dep:@types/readable-stream | AI (phantom-deps): @types/readable-stream is a TypeScript type package; not directly imported at runtime by convention. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.5.5 | 4 / 15 | |
| 2.5.4 | 4 / 15 | |
| 2.5.3 | 3 / 15 | |
| 2.5.2 | 3 / 9 | |
| 2.5.1 | 3 / 9 | |
| 2.5.0 | 3 / 9 | |
| 2.4.1 | 3 / 9 | |
| 2.4.0 | 3 / 9 | |
| 2.3.1 | 3 / 9 | |
| 2.3.0 | 3 / 9 | |
| 2.2.0 | 2 / 9 | |
| 2.1.1 | 2 / 9 | |
| 2.1.0 | 2 / 9 | |
| 2.0.0 | 2 / 8 |
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
2 findingsThis version was published by a different npm account (leftiefriele) than the most recent previously approved version (digitalsadhu) on 2023-09-19. It has since remained available on npm for 1036 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (digitalsadhu) than the most recent previously approved version (trygve) on 2019-10-03, but digitalsadhu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (trygve) than the most recent previously approved version (digitalsadhu) on 2019-03-07, but trygve is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (digitalsadhu) than the most recent previously approved version (trygve) on 2019-01-21, but digitalsadhu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.