← Home

@gjsify/dom-elements

npm Repository Homepage
3
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jumplinkschanzewlsh

Keywords

gjsdomelementnode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@gjsify/fetch AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires because it's re-exported rather than directly imported. ai
phantom-deps phantom-dep:@gjsify/abort-controller AI (phantom-deps): Same-org dependency; stable false positive for this package. ai
phantom-deps phantom-dep:@girs/gjs AI (phantom-deps): Referenced in config/type declarations, not direct imports; stable false positive for GJS type-binding packages. ai
provenance no-provenance AI (provenance): Consistent across all @gjsify packages; not a security concern for this org. ai

Versions (showing 3 of 3)

Version Deps Published
0.4.0 7 / 5
0.3.20 7 / 5
0.1.4 7 / 4

v0.4.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.

v0.3.20

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.

v0.1.4

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.