tctx
6
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
marais
Keywords
tracecontexttraceparentdistributedtracingw3c
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 manual publish to GitHub Actions CI/CD with SLSA attestation; expected for this package going forward. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD adoption with SLSA attestation; no malicious indicators present. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 1 / 0 | |
| 0.2.5 | 1 / 0 | |
| 0.2.4 | 1 / 0 | |
| 0.2.3 | 1 / 1 | |
| 0.2.2 | 1 / 1 | |
| 0.2.1 | 1 / 1 |
v0.2.4
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.