@microsoft/eslint-plugin-spfx
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-releaseskevintcoughlinodspnpm
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft release automation account; consistent with org-wide publishing practices. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft SPFx tooling package; provenance absence is consistent across all versions and not a risk indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft SPFx tooling package; sparse README/keywords are typical for enterprise SDK components. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 2 / 6 | |
| 1.23.1 | 2 / 6 | |
| 1.23.0 | 2 / 6 | |
| 1.22.2 | 2 / 12 | |
| 1.22.1 | 2 / 12 | |
| 1.22.0 | 2 / 12 | |
| 1.21.1 | 1 / 12 | |
| 1.21.0 | 1 / 12 | |
| 1.20.2 | 1 / 12 |
v1.23.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.