← Home

@ensdomains/ensjs

npm Repository
11
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

makoto_inouenickjohnsonjefflaumdt.leeondamikytaytemsadraffyv1rtl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:abitype AI (phantom-deps): abitype is a peer/type dependency used in config; stable false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
4.3.1 10 / 26
4.3.0 10 / 26
4.2.3 10 / 26
4.2.2 10 / 26
4.2.0 10 / 27
4.1.2 10 / 27
4.1.1 10 / 27
4.1.0 10 / 27
4.0.2 10 / 0
4.0.1 9 / 0
4.0.0 9 / 0

v4.0.2

2 findings
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.

INFO Publisher changed: taytems → dropthebeatbro (on 2024-11-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (dropthebeatbro) than the most recent previously approved version (taytems) on 2024-11-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v4.0.1

1 finding
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.

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