@microsoft/sp-dialog
SharePoint Framework support for displaying dialog boxes
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/sp-dialog_none_4a53cd066751572efef7.js | AI (source-diff): Webpack-bundled build output with hash-named chunk, consistent with normal SPFx build pipeline. | ai | |
| source-diff | obfuscated-file:dist/sp-dialog_none_c8e97e94fcdc1f39d4a4.js | AI (source-diff): Webpack-bundled build output, not true obfuscation; consistent with SPFx build tooling. | ai | |
| source-diff | obfuscated-file:dist/sp-dialog_none_d5b2f72a90c87772b4ae.js | AI (source-diff): Webpack-bundled SPFx module output, not true obfuscation; consistent with prior releases. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds official @fluentui/react-components, part of Microsoft's fluent UI migration. | ai | |
| source-diff | obfuscated-file:dist/sp-dialog_none_5eab3aa8a00fb26e9d42.js | AI (source-diff): Webpack/AMD bundle output for SPFx, not real obfuscation; consistent across Microsoft SPFx packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is Microsoft's OSS release automation account; consistent with org-wide release pipeline. | ai | |
| source-diff | obfuscated-file:dist/sp-dialog_none_69623abbc5403c90e5a7.js | AI (source-diff): Standard SPFx webpack bundle output; AMD define() with known Microsoft/FluentUI deps, not malicious obfuscation. | ai | |
| dependencies | unvetted-dep:@fluentui/react | AI (dependencies): @fluentui/react is the official Microsoft Fluent UI library; expected dependency for this SPFx dialog package. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft SPFx packages are published from internal pipelines without Sigstore attestation; stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft SPFx SDK component; sparse README/keywords are typical for this package family. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit SWC transpiler runtime dep; stable pattern for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 10 / 7 | |
| 1.23.1 | 10 / 7 | |
| 1.23.0 | 10 / 7 | |
| 1.22.2 | 10 / 7 | |
| 1.22.1 | 10 / 7 | |
| 1.22.0 | 10 / 7 | |
| 1.21.1 | 10 / 7 | |
| 1.21.0 | 10 / 7 | |
| 1.20.0 | 8 / 7 | |
| 1.19.0 | 7 / 7 |
v1.23.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2025-04-23, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.20.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2024-09-26, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.19.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.