safevalues
Safe builders for Trusted Types values
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dom/globals/global.mjs | AI (source-diff): safevalues wraps dangerous DOM APIs by design; globalEval is an intentional, documented wrapper around window.eval for SafeScript values. No actual network calls present — stable false positive for this package. | ai | |
| source-diff | net-exec-file:dom/globals/global.js | AI (source-diff): safevalues is a Google library providing safe wrappers for Trusted Types; eval() wrappers are its core purpose. No actual network calls present — false positive from DOM API usage. | ai | |
| provenance | missing-githead | AI (provenance): google-wombot is Google's established publishing bot; missing gitHead reflects a CI/CD tooling change, not a supply chain compromise. Package has 31 versions and strong ecosystem trust. | ai | |
| provenance | no-provenance | AI (provenance): Google's safevalues package predates widespread Sigstore adoption; absence of attestation is a process gap, not a security signal for this well-known package. | ai | |
| source-diff | net-exec-file:dist/mjs/dom/globals/global.js | AI (source-diff): ESM variant of the same safe wrapper around eval — identical rationale. Core library functionality for the safevalues trusted-types package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Google's safevalues library legitimately expands its DOM API coverage across versions; large file additions are expected as the library grows its safe-wrapper surface area. | ai | |
| source-diff | net-exec-file:dist/cjs/dom/globals/global.js | AI (source-diff): safevalues is a Google security library providing type-safe wrappers around dangerous APIs. globalEval wrapping win.eval() with SafeScript validation is core library functionality, not malware. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 10 | |
| 1.1.0 | 0 / 10 | |
| 1.0.1 | 0 / 10 | |
| 1.0.0 | 0 / 10 | |
| 0.7.0 | 0 / 11 | |
| 0.6.0 | 0 / 11 | |
| 0.5.2 | 0 / 11 | |
| 0.5.1 | 0 / 11 | |
| 0.5.0 | 0 / 11 | |
| 0.4.3 | 0 / 11 | |
| 0.4.2 | 0 / 11 | |
| 0.4.1 | 0 / 11 | |
| 0.4.0 | 0 / 11 | |
| 0.3.4 | 0 / 11 | |
| 0.3.3 | 0 / 11 | |
| 0.3.2 | 0 / 11 | |
| 0.3.1 | 0 / 11 | |
| 0.3.0 | 0 / 11 | |
| 0.2.0 | 0 / 11 | |
| 0.1.8 | 0 / 10 | |
| 0.1.7 | 0 / 10 | |
| 0.1.6 | 0 / 10 | |
| 0.1.5 | 0 / 9 | |
| 0.1.4 | 0 / 9 | |
| 0.1.3 | 0 / 9 | |
| 0.1.2 | 0 / 9 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
v0.3.3
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
v0.3.2
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
v0.2.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage 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.