@instana/metrics-util
Internal utility library for Instana metric collection
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 | AI (provenance): aryamohanan is a named contributor with IBM/Instana email; consistent with org-internal maintainer rotation. | ai | |
| dependencies | unvetted-dep:@instana/core | AI (dependencies): Internal Instana monorepo sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@instana/shared-metrics | AI (dependencies): Internal Instana monorepo sibling package; not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a risk indicator here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 6.5.0 | 2 / 0 | |
| 6.4.0 | 2 / 0 | |
| 6.3.0 | 2 / 0 | |
| 6.2.2 | 2 / 0 | |
| 6.2.1 | 2 / 0 | |
| 6.2.0 | 2 / 0 | |
| 6.1.1 | 2 / 0 | |
| 6.1.0 | 2 / 0 | |
| 6.0.0 | 2 / 0 | |
| 5.5.0 | 2 / 0 | |
| 5.4.3 | 2 / 0 | |
| 5.4.2 | 2 / 0 | |
| 5.4.1 | 2 / 0 | |
| 5.4.0 | 2 / 0 | |
| 5.3.0 | 2 / 0 | |
| 5.2.3 | 2 / 0 | |
| 5.2.2 | 2 / 0 | |
| 5.2.1 | 2 / 0 | |
| 5.2.0 | 2 / 0 | |
| 5.1.0 | 2 / 0 | |
| 5.0.2 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 4 / 0 | |
| 4.31.0 | 3 / 0 | |
| 4.30.1 | 3 / 0 | |
| 4.30.0 | 3 / 0 | |
| 4.29.0 | 3 / 0 | |
| 4.28.0 | 3 / 0 | |
| 4.27.1 | 3 / 0 |
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.