← Home

lock-verify

npm Repository Homepage

Report if your package.json is out of sync with your package-lock.json.

10
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

fritzydarcyclarkenlfgarlukekarrys

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Takeover reflects a legitimate transfer from iarna (Rebecca Turner) to the npm team (isaacs, adam_baldwin, etc.) — all well-known ecosystem contributors. Not a hijack. ai
publish-pattern new-deps-added AI (publish-pattern): @iarna/cli is scoped under the original author's namespace and is a natural CLI helper addition. Low supply-chain risk. ai
provenance publisher-changed AI (provenance): Publisher change from darcyclarke to gar reflects a documented npm org team transition; gar is a trusted, long-standing npm publisher. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (fritzy, nlf, gar, lukekarrys) are npm org team members added as part of a legitimate org restructuring. Stable for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers reflect npm org team changes, not a hostile takeover. Consistent with known 2022 npm org restructuring. Stable for this package. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by publish aligns with npm org team transition timeline, not account compromise. Package is under the official npm GitHub org. ai

Versions (showing 10 of 10)

Version Deps Published
2.2.2 3 / 0
2.2.1 3 / 0
2.2.0 3 / 0
2.1.0 2 / 1
2.0.2 2 / 1
2.0.1 2 / 1
2.0.0 2 / 1
1.1.0 3 / 0
1.0.1 3 / 0
1.0.0 3 / 0

v2.2.2

2 findings
HIGH Publisher changed: darcyclarke → gar (on 2022-11-16) provenance

This version was published by a different npm account than previous versions on 2022-11-16. 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.

v2.2.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: isaacs → darcyclarke (on 2020-07-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-23. This could indicate a legitimate maintainer transition or an account compromise.

v2.2.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (iarna) were replaced by new maintainers (adam_baldwin, ahmadnassri, claudiahdz, darcyclarke, isaacs, mikemimik, ruyadorno). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

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

INFO Publisher changed: iarna → isaacs (on 2020-01-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-30. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: iarna → zkat (on 2019-02-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-13. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

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. Consider requesting the maintainer enable provenance via CI/CD.

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.