← Home

@microsoft/sp-build-web

npm Homepage

SharePoint Framework build rig for web projects

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@microsoft/gulp-core-build-serve AI (dependencies): First-party Microsoft sibling package in the SPFx build toolchain. ai
dependencies unvetted-dep:@microsoft/gulp-core-build AI (dependencies): First-party Microsoft sibling package in the SPFx build toolchain. ai
dependencies unvetted-dep:@microsoft/gulp-core-build-sass AI (dependencies): First-party Microsoft sibling package in the SPFx build toolchain. ai
maintainer-change maintainer-added AI (maintainer-change): microsoft-oss-releases is Microsoft's standard OSS release automation account; consistent with org-wide release pipeline. ai
dependencies unvetted-dep:@microsoft/gulp-core-build-webpack AI (dependencies): First-party Microsoft sibling package in the SPFx build toolchain. ai
dependencies unvetted-dep:@microsoft/gulp-core-build-typescript AI (dependencies): First-party Microsoft sibling package in the SPFx build toolchain. ai
bogus-package bogus-package AI (bogus-package): Corporate Microsoft SDK with custom license/homepage; sparse README is typical for this package family, not spam. ai

Versions (showing 5 of 5)

Version Deps Published
1.23.0 10 / 4
1.22.2 10 / 4
1.22.1 10 / 4
1.22.0 10 / 4
1.21.1 10 / 4

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.