@stoplight/yaml
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
Keywords
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): Org-wide maintainer refresh on trusted package, no behavior change in diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added as roster cleanup, not takeover, given zero code diff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived stable package; dormancy then identical-content release is benign. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 4 / 0 | |
| 4.2.3 | 4 / 0 | |
| 4.2.2 | 4 / 0 | |
| 4.2.1 | 4 / 0 | |
| 4.2.0 | 4 / 0 | |
| 4.1.0 | 4 / 0 | |
| 4.0.2 | 4 / 0 | |
| 4.0.1 | 4 / 0 | |
| 4.0.0 | 4 / 0 |
v4.2.3
2 findingsThis version was published by a different npm account (stoplight-devops) than the most recent previously approved version (marbemac) on 2022-04-15. It has since remained available on npm for 1557 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.