@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yeoman-generator | AI (phantom-deps): Core generator dependency, likely extended via subclassing not detected by import scan. | ai | |
| 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 6 of 206)
| Version | Deps | Published |
|---|---|---|
| 56.0.6 | 6 / 14 | |
| 56.0.5 | 6 / 14 | |
| 56.0.4 | 6 / 14 | |
| 56.0.3 | 6 / 14 | |
| 56.0.2 | 6 / 14 | |
| 56.0.1 | 6 / 14 |
v56.0.6
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.0.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.0.4
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.0.3
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.0.2
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.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.