@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.3.53 | 9 / 9 | |
| 1.3.52 | 9 / 9 | |
| 1.3.51 | 9 / 9 | |
| 1.3.50 | 9 / 9 | |
| 1.3.49 | 9 / 9 | |
| 1.3.48 | 9 / 9 | |
| 1.3.47 | 9 / 9 | |
| 1.3.46 | 9 / 9 | |
| 1.3.43 | 9 / 9 | |
| 1.3.42 | 9 / 9 | |
| 1.3.41 | 9 / 9 | |
| 1.3.40 | 9 / 9 | |
| 1.3.39 | 9 / 9 | |
| 1.3.38 | 9 / 9 | |
| 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 | |
| 1.3.3 | 9 / 9 | |
| 1.3.2 | 9 / 9 | |
| 1.3.1 | 9 / 9 | |
| 1.3.0 | 9 / 9 | |
| 1.2.2 | 8 / 9 |
v1.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.