@traceloop/instrumentation-anthropic
Supply chain provenance
Status for the latest visible version.
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): Transition from individual publisher to GitHub Actions CI/CD with SLSA provenance; legitimate automation change. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): @opentelemetry/core is a legitimate runtime dependency declared in package.json; the phantom-dep finding is a false positive as it's used in config/build context rather than direct imports. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 7 / 10 | |
| 0.26.0 | 7 / 10 | |
| 0.25.0 | 7 / 10 | |
| 0.24.0 | 7 / 10 | |
| 0.23.0 | 7 / 10 | |
| 0.22.6 | 6 / 10 | |
| 0.22.5 | 6 / 9 | |
| 0.22.2 | 6 / 9 | |
| 0.22.0 | 6 / 9 | |
| 0.21.0 | 6 / 9 | |
| 0.20.0 | 6 / 9 | |
| 0.19.0 | 6 / 9 | |
| 0.18.0 | 6 / 9 | |
| 0.17.1 | 6 / 9 | |
| 0.17.0 | 6 / 9 | |
| 0.16.0 | 6 / 9 | |
| 0.15.0 | 6 / 9 | |
| 0.14.6 | 6 / 9 | |
| 0.14.5 | 6 / 9 | |
| 0.14.4 | 5 / 9 | |
| 0.14.3 | 5 / 7 | |
| 0.14.0 | 5 / 7 | |
| 0.13.4 | 5 / 7 |
v0.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.