yaml-loader
YAML loader for Webpack
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): Known handoff to contributor eemeli, long-established and stable. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale, long-stable transfer, not an active takeover pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with strong track record; lack of provenance attestation is common and not a risk indicator for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 2 / 6 | |
| 0.8.1 | 3 / 5 | |
| 0.8.0 | 3 / 2 | |
| 0.7.0 | 3 / 2 | |
| 0.6.0 | 2 / 2 | |
| 0.5.0 | 1 / 0 | |
| 0.4.0 | 1 / 0 | |
| 0.3.0 | 1 / 0 | |
| 0.2.0 | 1 / 0 | |
| 0.1.0 | 1 / 0 |
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version was published by a different npm account (eemeli) than the most recent previously approved version (okonet) on 2022-04-09. It has since remained available on npm for 1562 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.6.0
2 findingsThis version was published by a different npm account (eemeli) than the most recent previously approved version (okonet) on 2020-03-21. It has since remained available on npm for 2311 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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.