← Home

is-ci

npm Repository Homepage

Detect if the current environment is a CI server

19
Versions
MIT
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

watsonsibiraj-s

Keywords

cicontinuousintegrationtestdetect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from watson to sibiraj-s; sibiraj-s has a clean long-standing track record and no code changes are suspicious. ai
maintainer-change maintainer-added AI (maintainer-change): sibiraj-s added as maintainer in a legitimate transfer; clean history (57 approved, 0 rejected). ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; absence is expected for this era of publishing. ai

Versions (showing 19 of 19)

Version Deps Published
4.1.0 1 / 2
4.0.0 1 / 2
3.0.1 1 / 2
3.0.0 1 / 2
2.0.0 1 / 2
1.2.1 1 / 2
1.2.0 1 / 2
1.1.0 1 / 2
1.0.10 1 / 2
1.0.9 0 / 2
1.0.8 0 / 2
1.0.7 0 / 2
1.0.6 0 / 2
1.0.5 0 / 2
1.0.4 0 / 1
1.0.3 0 / 1
1.0.2 0 / 1
1.0.1 0 / 1
1.0.0 0 / 1

v4.0.0

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

2 findings
HIGH Publisher changed: watson → sibiraj-s (on 2021-02-18) provenance

This version was published by a different npm account than previous versions on 2021-02-18. 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.

v1.2.1

1 finding
LOW No provenance attestation provenance

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