libcipm — Greenflagged

programmatic API for cipm: a ci-oriented package installer for npm

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

adam_baldwinclaudiahdzdarcyclarkeisaacsruyadorno

Keywords

npmpackage managercachingdownloader

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Transition from zkat to isaacs is a known legitimate handoff; isaacs is the original npm author with a strong trust record. Not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): isaacs is a highly trusted npm ecosystem maintainer; addition is part of a known legitimate transition.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): zkat's removal is part of the same known legitimate maintainer transition to isaacs.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from isaacs to claudiahdz occurred in 2019 as a legitimate npm org maintainer transition. claudiahdz is a well-established publisher with a strong track record.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): libcipm is a package installer that legitimately spawns child processes to run lifecycle scripts. child_process usage is expected and appropriate for this tool.	ai	2026/04/24

Versions (showing 32 of 32)

Version	Deps	Published
4.0.8	15 / 7	2020-03-25
4.0.7	15 / 9	2019-10-09
4.0.4	15 / 9	2019-09-24
4.0.3	15 / 9	2019-08-12
4.0.2	15 / 9	2019-08-12
4.0.1	15 / 9	2019-08-12
4.0.0	15 / 9	2019-07-10
3.0.3	15 / 9	2019-01-22
3.0.2	15 / 9	2018-08-31
3.0.1	15 / 9	2018-08-31
3.0.0	15 / 9	2018-08-31
2.0.2	14 / 9	2018-08-10
2.0.1	14 / 9	2018-07-27
2.0.0	13 / 10	2018-05-24
1.6.3	13 / 10	2018-05-24
1.6.2	13 / 10	2018-04-08
1.6.1	13 / 10	2018-03-13
1.6.0	13 / 10	2018-03-01
1.5.1	13 / 10	2018-03-01
1.5.0	13 / 10	2018-03-01
1.4.1	13 / 10	2018-02-27
1.4.0	13 / 9	2018-02-22
1.3.3	13 / 9	2018-02-21
1.3.2	13 / 9	2018-02-15
1.3.1	13 / 9	2018-02-15
1.3.0	13 / 9	2018-02-13
1.2.0	13 / 9	2018-02-07
1.1.2	13 / 9	2018-01-19
1.1.1	13 / 9	2018-01-19
1.1.0	13 / 9	2018-01-07
1.0.1	13 / 9	2018-01-07
1.0.0	12 / 9	2018-01-07

v4.0.8

2 findings

HIGH Publisher changed: claudiahdz → isaacs (on 2020-03-25) provenance

This version was published by a different npm account than previous versions on 2020-03-25. 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.

v4.0.7

2 findings

HIGH Publisher changed: isaacs → claudiahdz (on 2019-10-09) provenance

This version was published by a different npm account than previous versions on 2019-10-09. 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.

v4.0.4

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (zkat) were replaced by new maintainers (adam_baldwin, ahmadnassri, annekimsey, claudiahdz, darcyclarke, isaacs). 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: zkat → isaacs (on 2019-08-12) provenance

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

v4.0.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (zkat) were replaced by new maintainers (isaacs). 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: zkat → isaacs (on 2019-07-10) provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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