supertest — Greenflagged

SuperAgent driven library for testing HTTP servers

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

niftylettucetjholowaychukkofdefunctzombiemikelaxtitanism

Keywords

bddhttprequestsuperagenttddtesttesting

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): supertest is a long-established package; missing gitHead reflects a publish environment change but no code/dep changes exist vs prior version. Not a reliable malice indicator for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): supertest is a long-established package; lack of Sigstore attestation is a hygiene concern, not a security risk for this well-known library.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): niftylettuce is a long-standing npm publisher (3451 days) with a strong track record; the transition from rimiti appears to be a legitimate maintainer handoff with no code changes.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer niftylettuce has an established npm history; no suspicious code or script changes accompany this maintainer addition.	ai	2026/04/24

Versions (showing 51 of 75)

View all versions

Version	Deps	Published
7.2.2	3 / 14	2026-01-06
7.2.1	3 / 14	2026-01-06
7.2.0	3 / 14	2026-01-06
7.1.4	2 / 13	2025-07-22
7.1.3	2 / 13	2025-07-07
7.1.2	2 / 13	2025-07-07
7.1.1	2 / 13	2025-05-12
7.1.0	2 / 13	2025-03-20
7.0.0	2 / 11	2024-04-24
6.3.4	2 / 11	2024-01-14
6.3.3	2 / 11	2022-12-07
6.3.2	2 / 11	2022-12-02
6.3.1	2 / 11	2022-10-24
6.3.0	2 / 11	2022-10-04
6.2.4	2 / 11	2022-07-01
6.2.3	2 / 11	2022-04-26
6.2.2	2 / 11	2022-01-18
6.2.1	2 / 11	2022-01-11
6.2.0	2 / 11	2022-01-10
6.1.6	2 / 11	2021-08-17
6.1.5	2 / 11	2021-08-11
6.1.4	2 / 11	2021-07-21
6.1.3	2 / 11	2021-01-25
6.1.2	2 / 11	2021-01-25
6.1.1	2 / 11	2021-01-15
6.1.0	2 / 11	2021-01-15
6.0.1	2 / 11	2020-11-04
6.0.0	2 / 11	2020-10-28
5.0.0	2 / 11	2020-09-25
4.0.2	2 / 11	2019-03-15
4.0.1	2 / 11	2019-03-15
4.0.0	2 / 11	2019-03-09
3.4.2	2 / 11	2019-01-22
3.4.1	2 / 11	2019-01-16
3.4.0	2 / 10	2019-01-16
3.3.0	2 / 11	2018-09-06
3.2.0	2 / 11	2018-09-05
3.1.0	2 / 11	2018-05-13
3.0.0	2 / 10	2017-01-30
2.0.1	2 / 10	2016-10-19
2.0.0	2 / 7	2016-07-29
1.2.0	2 / 5	2016-02-11
1.1.0	2 / 5	2015-08-26
1.0.1	2 / 4	2015-05-13
1.0.0	2 / 4	2015-05-12
0.15.0	2 / 3	2014-11-11
0.14.0	2 / 3	2014-09-29
0.13.0	2 / 3	2014-05-23
0.12.1	2 / 3	2014-05-09
0.12.0	2 / 3	2014-04-30
0.11.0	2 / 3	2014-04-14

v7.2.2

1 finding

LOW No provenance attestation provenance

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

v7.2.1

1 finding

LOW No provenance attestation provenance

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

v7.2.0

1 finding

LOW No provenance attestation provenance

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

v7.1.4

1 finding

LOW No provenance attestation provenance

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

v7.1.3

1 finding

LOW No provenance attestation provenance

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

v7.1.2

1 finding

LOW No provenance attestation provenance

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

v7.1.1

1 finding

LOW No provenance attestation provenance

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

v7.1.0

1 finding

LOW No provenance attestation provenance

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

v7.0.0

1 finding

LOW No provenance attestation provenance

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

v6.3.4

1 finding

LOW No provenance attestation provenance

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

v6.3.3

1 finding

INFO No provenance attestation provenance

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

v6.3.2

1 finding

LOW No provenance attestation provenance

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

v6.3.1

1 finding

INFO No provenance attestation provenance

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

v6.3.0

1 finding

INFO No provenance attestation provenance

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

v6.2.4

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: niftylettuce → titanism (on 2022-07-01) provenance

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

v6.2.3

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: titanism.

LOW No provenance attestation provenance

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

INFO Publisher changed: niftylettuce → titanism (on 2022-04-26) provenance

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

v6.2.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: niftylettuce.

LOW No provenance attestation provenance

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

v6.2.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: niftylettuce.

INFO No provenance attestation provenance

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

v6.2.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: niftylettuce.

INFO No provenance attestation provenance

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

v6.1.6

1 finding

LOW No provenance attestation provenance

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

v6.1.5

1 finding

LOW No provenance attestation provenance

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

v6.1.4

1 finding

INFO No provenance attestation provenance

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

v6.1.3

1 finding

LOW No provenance attestation provenance

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

v6.1.2

1 finding

LOW No provenance attestation provenance

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

v6.1.1

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.1

1 finding

LOW No provenance attestation provenance

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

v6.0.0

2 findings

HIGH Publisher changed: rimiti → niftylettuce (on 2020-10-28) provenance

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