@instana/shared-metrics
Internal metrics plug-in package for Node.js monitoring with Instana
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
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 email; transition appears legitimate for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active monorepo with 254 versions; dormancy flag is a false positive for this package's release cadence. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Intentional pattern for http/https module instrumentation by name; stable across versions of this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 5 / 1 | |
| 6.0.0 | 5 / 1 | |
| 5.5.0 | 5 / 1 | |
| 5.4.3 | 5 / 1 | |
| 5.4.2 | 5 / 1 | |
| 5.4.1 | 5 / 1 | |
| 5.4.0 | 5 / 1 | |
| 5.3.0 | 5 / 1 | |
| 5.2.3 | 5 / 1 | |
| 5.2.2 | 5 / 1 | |
| 5.2.1 | 5 / 1 | |
| 5.2.0 | 5 / 1 | |
| 5.1.0 | 5 / 1 | |
| 5.0.2 | 5 / 1 | |
| 5.0.1 | 5 / 1 | |
| 4.31.0 | 5 / 1 | |
| 4.30.1 | 5 / 1 | |
| 4.30.0 | 5 / 1 | |
| 4.29.0 | 5 / 1 | |
| 4.28.0 | 5 / 1 | |
| 4.27.1 | 5 / 1 |
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. 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.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. 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.
v4.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.