@stoplight/yaml-ast-parser
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-takeover | AI (maintainer-change): Long-stable org migration, not a fresh takeover; publisher unchanged across many versions since. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Same stale org-migration explanation; stable for 1552 days. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is an intentional feature for YAML !!js/function type handling, inherited from js-yaml. The eslint-disable comment confirms deliberate use. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; absence is expected for packages of this age and does not indicate risk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.50 | 0 / 8 | |
| 0.0.49 | 0 / 8 | |
| 0.0.48 | 0 / 8 | |
| 0.0.47 | 0 / 8 | |
| 0.0.46 | 0 / 8 | |
| 0.0.45 | 0 / 8 | |
| 0.0.44 | 0 / 8 | |
| 0.0.43 | 0 / 8 |
v0.0.49
2 findingsThis version was published by a different npm account (stoplight-devops) than the most recent previously approved version (p0lip) on 2022-04-20. It has since remained available on npm for 1552 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.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mallachari) than the most recent previously approved version (p0lip) on 2020-03-20, but mallachari is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.