← Home

@traceloop/instrumentation-anthropic

npm Repository Homepage
37
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

tomer-friedmannirgagalklm

Keywords

opentelemetrynodejstracingopenaianthropic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 37 of 37)

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
0.13.0 5 / 6
0.12.0 5 / 6
0.11.6 5 / 6
0.11.1 5 / 6
0.11.0 5 / 6
0.10.0 5 / 6
0.9.2 5 / 6
0.9.0 4 / 6
0.8.8 4 / 6
0.8.6 4 / 6
0.8.0 4 / 6
0.7.0 4 / 6
0.6.1 4 / 6
0.6.0 4 / 6

v0.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.