@instana/core
Core library for Instana's Node.js packages
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): New publisher aryamohanan is a named contributor (IBM email) in package.json; consistent with internal team transition. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped IBM/Instana APM package; no resemblance to 'cors' in purpose or namespace. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Plugin/metrics module loader pattern; stable across versions of this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding AWS Lambda ClientContext per AWS SDK contract; not malicious payload handling. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 6.5.0 | 18 / 0 | |
| 6.4.0 | 18 / 0 | |
| 6.3.0 | 18 / 0 | |
| 6.2.2 | 18 / 0 | |
| 6.2.1 | 18 / 0 | |
| 6.2.0 | 18 / 0 | |
| 6.1.1 | 18 / 0 | |
| 6.1.0 | 18 / 0 | |
| 6.0.0 | 18 / 0 | |
| 5.5.0 | 18 / 0 | |
| 5.4.3 | 18 / 0 | |
| 5.4.2 | 18 / 0 | |
| 5.4.1 | 18 / 0 | |
| 5.4.0 | 18 / 0 | |
| 5.3.0 | 18 / 0 | |
| 5.2.3 | 18 / 0 | |
| 5.2.2 | 18 / 0 | |
| 5.2.1 | 18 / 0 | |
| 5.2.0 | 18 / 0 | |
| 5.1.0 | 18 / 0 | |
| 5.0.2 | 16 / 0 | |
| 5.0.1 | 16 / 0 | |
| 5.0.0 | 14 / 0 | |
| 4.31.0 | 16 / 0 | |
| 4.30.1 | 16 / 0 | |
| 4.30.0 | 16 / 0 | |
| 4.29.0 | 16 / 0 | |
| 4.28.0 | 16 / 0 | |
| 4.27.1 | 16 / 0 |
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.