@microsoft/sp-diagnostics
6
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
microsoft1esmicrosoft-oss-releasesodspnpm
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/sp-diagnostics_none_e1ab08ba097191a211b5.js | AI (source-diff): Standard webpack bundle for a Microsoft SPFx package; minification is expected, no malicious content. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft release automation account; consistent with org publishing practices. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft SPFx library; sparse README/keywords are typical for this package family. | ai | |
| license | uncommon-license:https://aka.ms/spfx/license | AI (license): Microsoft SPFx proprietary license; consistent across all versions of this package family. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 2 / 6 | |
| 1.22.2 | 2 / 6 | |
| 1.22.1 | 2 / 6 | |
| 1.22.0 | 2 / 6 | |
| 1.21.1 | 2 / 6 | |
| 1.19.0 | 2 / 4 |
v1.19.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.