← Home

@microsoft/generator-sharepoint

npm Homepage

Yeoman generator for the SharePoint Framework

5
Versions
https://aka.ms/spfx/license
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

microsoft1esmicrosoft-oss-releasesodspnpm

Keywords

yeoman-generator

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 5 of 5)

Version Deps Published
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

v1.23.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.22.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.22.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.21.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.