nssocket — Greenflagged

An elegant way to define lightweight protocols on-top of TCP/TLS sockets in node.js

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

indexzerogenediazjr

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Both hij1nx and indexzero are Nodejitsu employees listed as co-maintainers in package.json with @nodejitsu.com emails; this is a legitimate intra-org transition.	ai	2026/04/24
source-diff	obfuscated-file:lib-cov/nssocket.js	AI (source-diff): File is explicitly auto-generated by JSCoverage for test coverage instrumentation, as stated in its header comment. Not malicious obfuscation.	ai	2026/04/24

Versions (showing 23 of 23)

Version	Deps	Published
0.6.0	2 / 2	2015-12-18
0.5.3	2 / 2	2014-12-06
0.5.2	2 / 2	2014-11-11
0.5.1	2 / 1	2013-04-27
0.5.0	2 / 1	2013-04-21
0.4.0	2 / 2	2013-04-21
0.3.8	2 / 1	2012-05-24
0.3.7	2 / 1	2012-02-14
0.3.6	2 / 1	2012-02-02
0.3.5	2 / 1	2012-01-05
0.3.4	2 / 1	2011-11-26
0.3.3	2 / 1	2011-10-26
0.3.2	2 / 1	2011-10-18
0.3.1	1 / 1	2011-10-15
0.3.0	1 / 1	2011-10-14
0.2.5	1 / 1	2011-08-09
0.2.4	1 / 1	2011-08-08
0.2.3	1 / 1	2011-08-05
0.2.2	1 / 1	2011-08-03
0.2.1	1 / 1	2011-08-02
0.2.0	1 / 1	2011-07-29
0.1.1	1 / 1	2011-07-21
0.1.0	1 / 1	2011-07-21

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.3

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: genediazjr → indexzero (on 2014-12-06) provenance

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

v0.5.2

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: indexzero → genediazjr (on 2014-11-11) provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

3 findings

HIGH Publisher changed: hij1nx → indexzero (on 2013-04-21) provenance

This version was published by a different npm account than previous versions on 2013-04-21. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: lib-cov/nssocket.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

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: indexzero → hij1nx (on 2012-02-02) provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.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: indexzero → hij1nx (on 2011-11-26) provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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.