@salesforce/telemetry
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Salesforce-releases is a known, trusted publisher with 1103 approved packages. Lack of Sigstore provenance is a minor gap, not a security concern for this established package. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 6.8.27 | 7 / 3 | |
| 6.8.26 | 7 / 3 | |
| 6.8.25 | 7 / 3 | |
| 6.8.24 | 7 / 3 | |
| 6.8.23 | 7 / 3 | |
| 6.8.22 | 7 / 3 | |
| 6.8.21 | 7 / 3 | |
| 6.8.20 | 7 / 3 | |
| 6.8.19 | 7 / 3 | |
| 6.8.18 | 7 / 3 | |
| 6.8.17 | 7 / 3 | |
| 6.8.16 | 7 / 3 | |
| 6.8.15 | 7 / 3 | |
| 6.8.14 | 7 / 3 | |
| 6.8.13 | 7 / 3 | |
| 6.8.12 | 7 / 3 | |
| 6.8.11 | 7 / 3 | |
| 6.8.10 | 7 / 3 | |
| 6.8.9 | 7 / 3 | |
| 6.8.8 | 7 / 3 | |
| 6.8.7 | 7 / 3 | |
| 6.8.6 | 7 / 3 | |
| 6.8.5 | 7 / 3 | |
| 6.8.4 | 7 / 3 | |
| 6.8.3 | 7 / 3 | |
| 6.8.2 | 7 / 3 | |
| 6.8.1 | 7 / 3 | |
| 6.8.0 | 7 / 3 | |
| 6.7.3 | 7 / 3 | |
| 6.7.2 | 7 / 3 | |
| 6.7.1 | 7 / 3 | |
| 6.7.0 | 7 / 3 | |
| 6.6.7 | 7 / 3 | |
| 6.6.6 | 7 / 3 | |
| 6.6.5 | 7 / 3 | |
| 6.6.4 | 7 / 3 | |
| 6.6.3 | 7 / 3 | |
| 6.6.2 | 7 / 3 | |
| 6.6.1 | 7 / 3 | |
| 6.6.0 | 7 / 3 | |
| 6.5.2 | 6 / 3 | |
| 6.5.1 | 6 / 3 | |
| 6.5.0 | 6 / 3 | |
| 6.4.8 | 6 / 3 | |
| 6.4.7 | 6 / 3 | |
| 6.4.6 | 6 / 3 | |
| 6.4.5 | 6 / 3 | |
| 6.4.3 | 6 / 3 | |
| 6.4.2 | 6 / 3 | |
| 6.4.1 | 6 / 3 | |
| 6.4.0 | 6 / 3 |
v6.8.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.8.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.