@salesforce/source-tracking
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:isomorphic-git | AI (dependencies): isomorphic-git is a well-known pure-JS git library; its use is appropriate and expected in a source-tracking package that needs git operations. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 7.8.16 | 8 / 9 | |
| 7.8.15 | 8 / 9 | |
| 7.8.14 | 8 / 9 | |
| 7.8.13 | 8 / 9 | |
| 7.8.12 | 8 / 9 | |
| 7.8.11 | 8 / 9 | |
| 7.8.10 | 8 / 9 | |
| 7.8.9 | 8 / 9 | |
| 7.8.8 | 8 / 9 | |
| 7.8.7 | 8 / 9 | |
| 7.8.6 | 8 / 9 | |
| 7.8.5 | 8 / 9 | |
| 7.8.4 | 8 / 9 | |
| 7.8.3 | 8 / 9 | |
| 7.8.2 | 8 / 9 | |
| 7.8.1 | 8 / 9 | |
| 7.8.0 | 8 / 9 | |
| 7.7.0 | 8 / 9 | |
| 7.6.0 | 8 / 9 | |
| 7.5.2 | 8 / 9 | |
| 7.5.1 | 8 / 9 | |
| 7.5.0 | 8 / 9 | |
| 7.4.10 | 9 / 9 | |
| 7.4.9 | 9 / 10 | |
| 7.4.8 | 9 / 10 | |
| 7.4.7 | 9 / 10 | |
| 7.4.6 | 9 / 10 | |
| 7.4.5 | 9 / 10 | |
| 7.4.4 | 9 / 10 | |
| 7.4.3 | 9 / 10 | |
| 7.4.2 | 9 / 10 | |
| 7.4.1 | 9 / 10 | |
| 7.4.0 | 9 / 10 | |
| 7.3.25 | 9 / 10 | |
| 7.3.24 | 9 / 10 | |
| 7.3.23 | 9 / 10 |
v7.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.