← Home

@gjsify/string_decoder

45
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jumplinkschanzewlsh

Keywords

gjsnodestring_decoder

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@gjsify/buffer AI (phantom-deps): Same-org scoped dep, likely used indirectly via polyfill build. ai
provenance publisher-changed AI (provenance): CI migration to GitHub Actions publisher across monorepo, not account compromise. ai
phantom-deps phantom-dep:@gjsify/utils AI (phantom-deps): Same-org runtime dep declared in package.json; stable false positive for this package. ai
semgrep semgrep:hex-decode AI (semgrep): All hex-decode hits are in test spec files testing UTF-8 byte sequences; not runtime payload obfuscation. ai
dependencies unvetted-dep:@gjsify/utils AI (dependencies): Same @gjsify org dependency; consistent with the package's ecosystem pattern across all versions. ai

Versions (showing 45 of 45)

Version Deps Published
0.14.0 1 / 4
0.4.26 1 / 4
0.4.9 1 / 4
0.4.5 1 / 4
0.4.4 1 / 4
0.4.3 1 / 4
0.4.0 1 / 4
0.3.21 1 / 4
0.3.20 1 / 4
0.3.19 1 / 4
0.3.18 1 / 4
0.3.17 1 / 4
0.3.16 1 / 4
0.3.15 1 / 4
0.3.14 1 / 4
0.3.13 1 / 4
0.3.12 1 / 4
0.3.11 1 / 4
0.3.10 1 / 4
0.3.9 1 / 4
0.3.8 1 / 4
0.3.7 1 / 4
0.3.6 1 / 4
0.3.5 1 / 4
0.3.4 1 / 4
0.3.3 1 / 4
0.3.2 1 / 4
0.3.1 1 / 4
0.3.0 1 / 4
0.2.0 1 / 4
0.1.15 1 / 4
0.1.13 1 / 4
0.1.12 1 / 4
0.1.11 1 / 4
0.1.10 1 / 4
0.1.9 1 / 4
0.1.8 1 / 4
0.1.7 1 / 4
0.1.6 1 / 4
0.1.5 1 / 4
0.1.4 1 / 4
0.1.3 1 / 4
0.1.2 1 / 4
0.1.1 1 / 4
0.1.0 1 / 4

v0.14.0

3 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.

HIGH Publisher changed: jumplink → GitHub Actions (on 2026-06-29) provenance

This version was published by a different npm account than previous versions on 2026-06-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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