fstream-npm — Greenflagged

fstream class for creating npm packages

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

iarnaisaacsothiym23zkat

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from iarna to othiym23 occurred in 2015; othiym23 is a known npm core contributor. This is a historical, legitimate maintainer transition, not a compromise.	ai	2026/04/24

Versions (showing 25 of 25)

Version	Deps	Published
1.2.1	2 / 5	2017-05-13
1.2.0	2 / 5	2016-09-07
1.1.1	2 / 5	2016-08-02
1.1.0	2 / 5	2016-05-17
1.0.7	2 / 5	2015-11-05
1.0.6	2 / 5	2015-11-05
1.0.5	2 / 5	2015-08-20
1.0.3	2 / 1	2015-06-19
1.0.1	2 / 0	2014-10-17
1.0.0	2 / 0	2014-07-31
0.1.8	2 / 0	2014-07-31
0.1.7	2 / 0	2014-05-19
0.1.6	2 / 0	2013-10-11
0.1.5	2 / 0	2013-05-29
0.1.4	2 / 0	2013-03-10
0.1.3	2 / 0	2012-10-22
0.1.2	2 / 0	2012-09-10
0.1.1	2 / 0	2012-07-13
0.1.0	2 / 0	2012-06-04
0.0.6	2 / 0	2012-06-04
0.0.5	2 / 0	2012-04-17
0.0.4	2 / 0	2012-03-27
0.0.3	2 / 0	2012-03-27
0.0.2	1 / 0	2012-03-27
0.0.1	1 / 0	2012-03-27

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.

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

2 findings

HIGH Publisher changed: iarna → zkat (on 2016-05-17) provenance

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

v1.0.7

3 findings

HIGH Publisher changed: iarna → othiym23 (on 2015-11-05) provenance

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

HIGH Unclaimed maintainer email domain: aoaioxxysz.net email-domain

Maintainer email '[email protected]' uses domain 'aoaioxxysz.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.0.6

2 findings

HIGH Publisher changed: iarna → othiym23 (on 2015-11-05) provenance

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

2 findings

HIGH Publisher changed: iarna → othiym23 (on 2015-08-20) provenance

This version was published by a different npm account than previous versions on 2015-08-20. 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.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

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. 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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

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.