@microsoft/sp-module-interfaces
9
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads local JSON schema files from __dirname; not arbitrary module loading. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetches a Microsoft-owned JSON schema URL for validation; not telemetry or exfiltration. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 2 / 5 | |
| 1.23.1 | 2 / 5 | |
| 1.23.0 | 2 / 5 | |
| 1.22.2 | 2 / 3 | |
| 1.22.1 | 2 / 3 | |
| 1.22.0 | 2 / 3 | |
| 1.21.1 | 2 / 3 | |
| 1.21.0 | 2 / 3 | |
| 1.20.2 | 2 / 3 |
v1.23.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
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.