@decantr/telemetry
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.8.1 | 0 / 0 | |
| 3.8.0 | 0 / 0 | |
| 3.4.0 | 0 / 0 | |
| 3.1.0 | 0 / 0 | |
| 3.0.2 | 0 / 0 | |
| 3.0.1 | 0 / 0 | |
| 3.0.0 | 0 / 0 | |
| 2.2.1 | 0 / 0 | |
| 2.2.0 | 0 / 0 | |
| 2.1.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v3.8.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (davidaimi) on 2026-07-09, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.