ci-info MIT 36 versions

ci-info

npm Repository Homepage

Get details about the current Continuous Integration environment

36

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

watsonsibiraj-s

Keywords

cicontinuousintegrationtestdetect

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher changed from sibiraj-s to GitHub Actions CI/CD with SLSA provenance. This is an automated release pipeline, not a suspicious takeover.	ai	2026/04/23

Versions (showing 36 of 36)

Version	Deps	Published
4.4.0	0 / 5	2026-01-29
4.3.1	0 / 5	2025-10-05
4.3.0	0 / 5	2025-07-06
4.2.0	0 / 5	2025-03-09
4.1.0	0 / 4	2024-11-12
4.0.0	0 / 4	2023-10-29
3.9.0	0 / 4	2023-10-04
3.8.0	0 / 4	2023-02-11
3.7.1	0 / 4	2023-01-02
3.7.0	0 / 4	2022-11-24
3.6.2	0 / 4	2022-11-22
3.6.1	0 / 3	2022-11-13
3.6.0	0 / 3	2022-11-13
3.5.0	0 / 3	2022-10-09
3.4.0	0 / 3	2022-09-09
3.3.2	0 / 3	2022-06-15
3.3.1	0 / 3	2022-05-11
3.3.0	0 / 3	2021-11-24
3.2.0	0 / 3	2021-05-26
3.1.1	0 / 3	2021-02-18
3.1.0	0 / 3	2021-02-18
3.0.0	0 / 3	2021-02-17
2.0.0	0 / 3	2018-12-05
1.6.0	0 / 3	2018-09-20
1.5.1	0 / 3	2018-09-09
1.5.0	0 / 3	2018-09-08
1.4.0	0 / 2	2018-08-20
1.3.1	0 / 2	2018-08-16
1.3.0	0 / 2	2018-08-14
1.2.0	0 / 2	2018-08-14
1.1.3	0 / 2	2018-03-12
1.1.2	0 / 2	2017-11-17
1.1.1	0 / 2	2017-09-05
1.1.0	0 / 2	2017-09-05
1.0.1	0 / 2	2017-09-04
1.0.0	0 / 2	2016-10-20

v4.3.1

2 findings

HIGH Publisher changed: sibiraj-s → GitHub Actions (on 2025-10-05) provenance

This version was published by a different npm account than previous versions on 2025-10-05. This could indicate a legitimate maintainer transition or an account compromise.

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

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v3.8.0

1 finding

LOW No provenance attestation provenance

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

v3.7.1

1 finding

LOW No provenance attestation provenance

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

v3.7.0

1 finding

LOW No provenance attestation provenance

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

v3.6.2

1 finding

LOW No provenance attestation provenance

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

v3.6.1

1 finding

LOW No provenance attestation provenance

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

v3.6.0

1 finding

LOW No provenance attestation provenance

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

v3.5.0

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.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.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: watson → sibiraj-s (on 2021-02-17) provenance

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

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.