@salesforce/packaging
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to handle binary API responses from Salesforce packaging APIs — standard data handling, not payload obfuscation. Stable pattern for this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used for safe dynamic property access with null fallback — idiomatic JS pattern, not API evasion. Stable for this package. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 4.25.1 | 14 / 7 | |
| 4.25.0 | 14 / 7 | |
| 4.24.3 | 14 / 7 | |
| 4.24.2 | 14 / 7 | |
| 4.24.1 | 14 / 7 | |
| 4.24.0 | 14 / 7 | |
| 4.23.0 | 14 / 7 | |
| 4.22.16 | 14 / 7 | |
| 4.22.15 | 14 / 7 | |
| 4.22.14 | 14 / 7 | |
| 4.22.13 | 14 / 7 | |
| 4.22.12 | 14 / 7 | |
| 4.22.11 | 14 / 7 | |
| 4.22.10 | 14 / 7 | |
| 4.22.9 | 14 / 7 | |
| 4.22.8 | 14 / 7 | |
| 4.22.7 | 14 / 7 | |
| 4.22.6 | 14 / 7 | |
| 4.22.5 | 14 / 7 | |
| 4.22.4 | 14 / 7 | |
| 4.22.3 | 14 / 7 | |
| 4.22.2 | 14 / 7 | |
| 4.22.1 | 14 / 7 | |
| 4.22.0 | 14 / 7 | |
| 4.21.12 | 14 / 7 | |
| 4.21.11 | 14 / 7 | |
| 4.21.10 | 14 / 7 | |
| 4.21.9 | 14 / 7 | |
| 4.21.8 | 14 / 7 | |
| 4.21.7 | 14 / 7 | |
| 4.21.6 | 14 / 7 | |
| 4.21.5 | 14 / 7 | |
| 4.21.4 | 14 / 7 | |
| 4.21.3 | 14 / 7 | |
| 4.21.2 | 14 / 7 | |
| 4.21.1 | 14 / 7 | |
| 4.21.0 | 14 / 7 | |
| 4.20.6 | 14 / 7 | |
| 4.20.5 | 14 / 7 | |
| 4.20.4 | 14 / 7 | |
| 4.20.3 | 14 / 7 | |
| 4.20.2 | 14 / 7 | |
| 4.20.1 | 14 / 7 | |
| 4.20.0 | 14 / 7 | |
| 4.19.0 | 14 / 7 | |
| 4.18.12 | 14 / 7 | |
| 4.18.11 | 14 / 7 | |
| 4.18.10 | 14 / 7 | |
| 4.18.9 | 14 / 7 | |
| 4.18.8 | 14 / 7 | |
| 4.18.7 | 14 / 7 |
v4.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.