@microsoft/generator-sharepoint
Yeoman generator for the SharePoint Framework
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:mem-fs | AI (phantom-deps): mem-fs is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rushstack/terminal | AI (phantom-deps): Declared runtime dep from same Rush Stack org; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@microsoft/spfx-heft-plugins | AI (phantom-deps): First-party Microsoft SPFx dep declared in package.json; phantom-dep heuristic false positive. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 10 / 14 | |
| 1.23.1 | 10 / 14 | |
| 1.23.0 | 10 / 14 | |
| 1.22.2 | 10 / 15 | |
| 1.22.1 | 10 / 15 | |
| 1.22.0 | 10 / 15 | |
| 1.21.1 | 10 / 13 | |
| 1.21.0 | 10 / 13 | |
| 1.20.0 | 9 / 11 | |
| 1.19.0 | 9 / 11 |
v1.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.