← Home

@rsbuild/plugin-yaml

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

chenjiahanhardfist3

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 is used to embed a WebAssembly binary (md4 hash) in the compiled yaml-loader bundle — not malicious. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decode is standard binary data handling in yaml-loader for binary YAML types — not malicious. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.0 1 / 10
1.0.5 0 / 11
1.0.4 0 / 11
1.0.3 0 / 11
1.0.2 0 / 11
1.0.1 0 / 11
1.0.0 0 / 11

v2.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.