socks-proxy-agent — Greenflagged

A SOCKS proxy `http.Agent` implementation for HTTP and HTTPS

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

tootallnatekikobeats

Keywords

agenthttphttpsproxysockssocks4socks4asocks5socks5h

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): GitHub Actions publish flow drops gitHead; SLSA attestation provides stronger provenance signal.	ai	2026/04/27
provenance	publisher-changed	AI (provenance): kikobeats is a listed contributor in package.json and has a long npm history (3632 days, 322 approved packages). This is a legitimate maintainer transition, not a compromise.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): kikobeats was already a contributor on this package before becoming a publisher; the transition is legitimate.	ai	2026/04/22
publish-pattern	new-deps-added	AI (publish-pattern): The added dep is `debug`, an extremely well-vetted and ubiquitous Node.js package. No meaningful risk for this package.	ai	2026/04/22
dependencies	unvetted-dep:socks	AI (dependencies): socks is the canonical SOCKS protocol library and the expected core dependency for socks-proxy-agent; this is a stable false positive for this package.	ai	2026/04/21

Versions (showing 32 of 32)

Version	Deps	Published
10.0.0	3 / 12	2026-04-01
9.0.0	3 / 12	2026-03-11
8.0.5	3 / 15	2024-12-07
8.0.4	3 / 15	2024-06-28
8.0.3	3 / 15	2024-03-30
8.0.2	3 / 15	2023-09-04
8.0.1	3 / 15	2023-05-05
8.0.0	3 / 15	2023-05-04
7.0.0	3 / 22	2022-05-31
6.2.1	3 / 22	2022-05-31
6.2.0	3 / 22	2022-04-17
6.1.1	3 / 17	2021-11-22
6.1.0	3 / 17	2021-09-15
6.0.0	3 / 17	2021-07-04
5.0.1	3 / 17	2021-06-21
5.0.0	3 / 17	2020-02-04
4.0.2	2 / 3	2019-03-09
4.0.1	2 / 3	2018-04-13
4.0.0	2 / 3	2018-03-29
3.0.1	2 / 3	2017-09-18
3.0.0	2 / 3	2017-06-13
2.1.1	3 / 3	2017-06-13
2.1.0	3 / 2	2017-05-25
2.0.0	3 / 2	2015-07-11
1.0.2	3 / 2	2015-07-01
1.0.1	3 / 1	2015-03-02
1.0.0	3 / 1	2015-02-12
0.1.2	3 / 1	2014-06-11
0.1.1	3 / 1	2014-04-09
0.1.0	3 / 1	2013-11-19
0.0.2	2 / 1	2013-07-24
0.0.1	2 / 1	2013-07-11

v10.0.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: GitHub Actions.

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.

v8.0.3

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: tootallnate.

LOW No provenance attestation provenance

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

v8.0.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: tootallnate.

LOW No provenance attestation provenance

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

v8.0.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: tootallnate.

LOW No provenance attestation provenance

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

v8.0.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: tootallnate.

LOW No provenance attestation provenance

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

v7.0.0

2 findings

HIGH Publisher changed: tootallnate → kikobeats (on 2022-05-31) provenance

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

v6.2.1

2 findings

HIGH Publisher changed: tootallnate → kikobeats (on 2022-05-31) provenance

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

v6.2.0

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: kikobeats.

HIGH Publisher changed: tootallnate → kikobeats (on 2022-04-17) provenance

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

v6.1.1

2 findings

HIGH Publisher changed: tootallnate → kikobeats (on 2021-11-22) provenance

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

v6.1.0

2 findings

HIGH Publisher changed: tootallnate → kikobeats (on 2021-09-15) provenance

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

v6.0.0

2 findings

HIGH Publisher changed: tootallnate → kikobeats (on 2021-07-04) provenance

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

v5.0.1

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

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

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

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.

v1.0.1

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.

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

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.

v0.1.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.

v0.0.2

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.

v0.0.1

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.