@microsoft/sp-office-ui-fabric-core
A supported set of Office UI Fabric Core definitions bundled for use in 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/office-ui-fabric-core_none_5690e531e1da619d7f0d.js | AI (source-diff): Standard webpack AMD bundle loading CSS from Microsoft's SharePoint CDN; expected artifact for this package. | ai | |
| dependencies | unvetted-dep:office-ui-fabric-core | AI (dependencies): office-ui-fabric-core is the explicit purpose of this wrapper package; its inclusion is intentional and stable. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript-compiled packages; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): SWC helpers are implicit runtime dependencies injected by the build toolchain; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:office-ui-fabric-core | AI (phantom-deps): This package explicitly wraps office-ui-fabric-core; referenced in config files is expected behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft SPFx component package; sparse README and no keywords are cosmetic issues, not spam indicators. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 3 / 4 | |
| 1.22.2 | 3 / 4 | |
| 1.22.1 | 3 / 4 | |
| 1.22.0 | 3 / 4 | |
| 1.21.1 | 3 / 4 |
v1.23.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.