@stoplight/spectral-ref-resolver
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Stoplight package published before Sigstore provenance was common; no security concern for this well-known ecosystem package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 5 / 0 | |
| 1.0.4 | 5 / 0 | |
| 1.0.3 | 5 / 0 | |
| 1.0.2 | 5 / 0 | |
| 1.0.1 | 5 / 0 | |
| 1.0.0 | 4 / 0 |
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (marbemac) on 2022-12-13. It has since remained available on npm for 1316 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (marbemac) on 2022-10-03. It has since remained available on npm for 1387 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.