@salesforce/plugin-api
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
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.3.37 | 9 / 9 | |
| 1.3.36 | 9 / 9 | |
| 1.3.35 | 9 / 9 | |
| 1.3.34 | 9 / 9 | |
| 1.3.33 | 9 / 9 | |
| 1.3.32 | 9 / 9 | |
| 1.3.31 | 9 / 9 | |
| 1.3.30 | 9 / 9 | |
| 1.3.29 | 9 / 9 | |
| 1.3.28 | 9 / 9 | |
| 1.3.27 | 9 / 9 | |
| 1.3.26 | 9 / 9 | |
| 1.3.25 | 9 / 9 | |
| 1.3.24 | 9 / 9 | |
| 1.3.23 | 9 / 9 | |
| 1.3.22 | 9 / 9 | |
| 1.3.21 | 9 / 9 | |
| 1.3.20 | 9 / 9 | |
| 1.3.19 | 9 / 9 | |
| 1.3.18 | 9 / 9 | |
| 1.3.17 | 9 / 9 | |
| 1.3.16 | 9 / 9 | |
| 1.3.15 | 9 / 9 | |
| 1.3.14 | 9 / 9 | |
| 1.3.13 | 9 / 9 | |
| 1.3.12 | 9 / 9 | |
| 1.3.11 | 9 / 9 | |
| 1.3.10 | 9 / 9 | |
| 1.3.9 | 9 / 9 | |
| 1.3.8 | 9 / 9 | |
| 1.3.7 | 9 / 9 | |
| 1.3.6 | 9 / 9 |
v1.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.