@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 100 of 206)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 56.3.45 | 3 / 10 | |
| 56.3.44 | 3 / 10 | |
| 56.3.43 | 3 / 10 | |
| 56.3.42 | 3 / 10 | |
| 56.3.41 | 3 / 10 | |
| 56.3.40 | 3 / 10 | |
| 56.3.39 | 3 / 10 | |
| 56.3.38 | 3 / 10 | |
| 56.3.37 | 3 / 10 | |
| 56.3.35 | 3 / 10 | |
| 56.3.34 | 3 / 10 | |
| 56.3.33 | 3 / 10 | |
| 56.3.32 | 3 / 10 | |
| 56.3.31 | 3 / 10 | |
| 56.3.30 | 3 / 10 | |
| 56.3.29 | 3 / 10 | |
| 56.3.28 | 3 / 10 | |
| 56.3.27 | 3 / 10 | |
| 56.3.26 | 3 / 10 | |
| 56.3.25 | 3 / 10 | |
| 56.3.24 | 3 / 10 | |
| 56.3.23 | 3 / 10 | |
| 56.3.22 | 3 / 10 | |
| 56.3.21 | 3 / 10 | |
| 56.3.20 | 3 / 10 | |
| 56.3.19 | 3 / 10 | |
| 56.3.18 | 3 / 10 | |
| 56.3.17 | 3 / 10 | |
| 56.3.16 | 3 / 10 | |
| 56.3.15 | 3 / 10 | |
| 56.3.14 | 3 / 10 | |
| 56.3.13 | 3 / 10 | |
| 56.3.12 | 3 / 10 | |
| 56.3.11 | 3 / 10 | |
| 56.3.10 | 3 / 10 | |
| 56.3.9 | 3 / 10 | |
| 56.3.8 | 3 / 10 | |
| 56.3.7 | 3 / 10 | |
| 56.3.6 | 3 / 10 | |
| 56.3.5 | 3 / 10 | |
| 56.3.4 | 3 / 10 | |
| 56.3.3 | 3 / 10 | |
| 56.3.2 | 3 / 10 | |
| 56.3.1 | 3 / 10 | |
| 56.3.0 | 3 / 10 | |
| 56.2.14 | 5 / 13 | |
| 56.2.13 | 6 / 13 | |
| 56.2.12 | 6 / 13 | |
| 56.2.11 | 6 / 13 | |
| 56.2.10 | 6 / 13 | |
| 56.2.9 | 6 / 13 | |
| 56.2.8 | 6 / 13 | |
| 56.2.7 | 6 / 13 | |
| 56.2.6 | 6 / 13 | |
| 56.2.5 | 6 / 13 | |
| 56.2.4 | 6 / 13 | |
| 56.2.3 | 6 / 13 | |
| 56.2.2 | 6 / 13 | |
| 56.2.1 | 6 / 13 | |
| 56.2.0 | 6 / 13 | |
| 56.1.1 | 6 / 13 | |
| 56.1.0 | 6 / 13 | |
| 56.0.25 | 6 / 13 | |
| 56.0.24 | 6 / 13 | |
| 56.0.23 | 6 / 13 | |
| 56.0.22 | 6 / 13 | |
| 56.0.21 | 6 / 13 | |
| 56.0.20 | 6 / 13 | |
| 56.0.19 | 6 / 13 | |
| 56.0.17 | 6 / 14 | |
| 56.0.16 | 6 / 14 | |
| 56.0.15 | 6 / 14 | |
| 56.0.14 | 6 / 14 | |
| 56.0.13 | 6 / 14 | |
| 56.0.12 | 6 / 14 | |
| 56.0.11 | 6 / 14 | |
| 56.0.10 | 6 / 14 | |
| 56.0.9 | 6 / 14 | |
| 56.0.8 | 6 / 14 | |
| 56.0.7 | 6 / 14 |
v56.3.45
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.44
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.43
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.42
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.41
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.40
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.39
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.38
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.37
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.35
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.34
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.33
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.32
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.31
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.30
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.29
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.28
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.27
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.26
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.25
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.24
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.23
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.22
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.21
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.20
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.19
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.18
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.17
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.16
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.15
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.14
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.13
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.12
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.11
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.10
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.9
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.8
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.7
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.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.3.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.3.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.3.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.3.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.3.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.
v56.3.0
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.2.14
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.2.13
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.2.12
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.2.11
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.2.10
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.2.9
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.2.8
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.2.7
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.2.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.2.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.2.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.2.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.2.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.2.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.
v56.2.0
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.1.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.
v56.1.0
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.25
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.24
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.23
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.22
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.21
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.20
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.19
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.17
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.16
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.15
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.14
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.13
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.12
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.11
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.10
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.9
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.8
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.