@salesforce/plugin-templates
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:@salesforce/templates | AI (dependencies): @salesforce/templates is the core first-party Salesforce template engine; it is the expected primary dependency for this plugin and stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce-releases publisher uses their own signing mechanism (sfdx publicKeyUrl/signatureUrl); lack of Sigstore provenance is acceptable for this established publisher. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 56.18.1 | 3 / 10 | |
| 56.18.0 | 3 / 10 | |
| 56.17.7 | 3 / 10 | |
| 56.17.6 | 3 / 10 | |
| 56.17.5 | 3 / 10 | |
| 56.17.4 | 3 / 10 | |
| 56.17.3 | 3 / 10 | |
| 56.17.2 | 3 / 10 | |
| 56.17.1 | 3 / 10 | |
| 56.17.0 | 3 / 10 | |
| 56.16.7 | 3 / 10 | |
| 56.16.6 | 3 / 10 | |
| 56.16.5 | 3 / 10 | |
| 56.16.4 | 3 / 10 | |
| 56.16.3 | 3 / 10 | |
| 56.16.2 | 3 / 10 | |
| 56.16.1 | 3 / 10 | |
| 56.16.0 | 3 / 10 | |
| 56.15.7 | 3 / 10 | |
| 56.15.6 | 3 / 10 | |
| 56.15.5 | 3 / 10 | |
| 56.15.4 | 3 / 10 | |
| 56.15.3 | 3 / 10 | |
| 56.15.2 | 3 / 10 | |
| 56.15.1 | 3 / 10 | |
| 56.15.0 | 3 / 10 | |
| 56.14.0 | 3 / 10 | |
| 56.13.4 | 3 / 10 | |
| 56.13.3 | 3 / 10 | |
| 56.13.2 | 3 / 10 | |
| 56.13.1 | 3 / 10 | |
| 56.13.0 | 3 / 10 | |
| 56.12.1 | 3 / 10 | |
| 56.12.0 | 3 / 10 | |
| 56.11.5 | 3 / 10 | |
| 56.11.4 | 3 / 10 | |
| 56.11.3 | 3 / 10 | |
| 56.11.2 | 3 / 10 | |
| 56.11.1 | 3 / 10 | |
| 56.11.0 | 3 / 10 | |
| 56.10.7 | 3 / 10 | |
| 56.10.6 | 3 / 10 | |
| 56.10.5 | 3 / 10 | |
| 56.10.4 | 3 / 10 | |
| 56.10.3 | 3 / 10 | |
| 56.10.2 | 3 / 10 | |
| 56.10.1 | 3 / 10 | |
| 56.10.0 | 3 / 10 | |
| 56.9.3 | 3 / 10 | |
| 56.9.2 | 3 / 10 | |
| 56.9.1 | 3 / 10 | |
| 56.9.0 | 3 / 10 | |
| 56.8.2 | 3 / 10 | |
| 56.8.1 | 3 / 10 | |
| 56.8.0 | 3 / 10 | |
| 56.7.2 | 3 / 10 | |
| 56.7.1 | 3 / 10 | |
| 56.7.0 | 3 / 10 | |
| 56.6.0 | 3 / 10 | |
| 56.5.2 | 3 / 10 | |
| 56.5.1 | 3 / 10 | |
| 56.5.0 | 3 / 10 | |
| 56.4.7 | 3 / 10 | |
| 56.4.6 | 3 / 10 | |
| 56.4.5 | 3 / 10 | |
| 56.4.4 | 3 / 10 | |
| 56.4.3 | 3 / 10 | |
| 56.4.2 | 3 / 10 | |
| 56.4.1 | 3 / 10 | |
| 56.4.0 | 3 / 10 | |
| 56.3.74 | 3 / 10 | |
| 56.3.73 | 3 / 10 | |
| 56.3.72 | 3 / 10 | |
| 56.3.71 | 3 / 10 | |
| 56.3.70 | 3 / 10 | |
| 56.3.69 | 3 / 10 | |
| 56.3.68 | 3 / 10 | |
| 56.3.66 | 3 / 10 | |
| 56.3.65 | 3 / 10 | |
| 56.3.64 | 3 / 10 | |
| 56.3.63 | 3 / 10 | |
| 56.3.62 | 3 / 10 | |
| 56.3.61 | 3 / 10 | |
| 56.3.60 | 3 / 10 | |
| 56.3.59 | 3 / 10 | |
| 56.3.58 | 3 / 10 | |
| 56.3.57 | 3 / 10 | |
| 56.3.56 | 3 / 10 | |
| 56.3.55 | 3 / 10 | |
| 56.3.54 | 3 / 10 | |
| 56.3.53 | 3 / 10 | |
| 56.3.52 | 3 / 10 | |
| 56.3.51 | 3 / 10 | |
| 56.3.50 | 3 / 10 | |
| 56.3.49 | 3 / 10 | |
| 56.3.48 | 3 / 10 | |
| 56.3.47 | 3 / 10 | |
| 56.3.46 | 3 / 10 |
v56.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v56.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.