@salesforce/plugin-marketplace
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Package is published by trusted salesforce-releases account; maintainer changes reflect internal Salesforce team reorganization, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal of individual Salesforce employee accounts in favor of consolidated maintainer is consistent with org-level npm access restructuring. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by publish under trusted salesforce-releases publisher with no code changes; consistent with package revival under consolidated Salesforce CLI team structure. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.3.29 | 5 / 8 | |
| 1.3.28 | 5 / 8 | |
| 1.3.27 | 5 / 8 | |
| 1.3.26 | 5 / 8 | |
| 1.3.25 | 5 / 8 | |
| 1.3.24 | 5 / 8 | |
| 1.3.23 | 5 / 8 | |
| 1.3.22 | 5 / 8 | |
| 1.3.21 | 5 / 8 | |
| 1.3.20 | 5 / 8 | |
| 1.3.19 | 5 / 8 | |
| 1.3.18 | 5 / 8 | |
| 1.3.17 | 5 / 8 | |
| 1.3.15 | 5 / 8 | |
| 1.3.14 | 5 / 8 | |
| 1.3.13 | 5 / 8 | |
| 1.3.12 | 5 / 8 | |
| 1.3.11 | 5 / 8 | |
| 1.3.10 | 5 / 8 | |
| 1.3.9 | 5 / 8 |
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.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.