read
read(1) for node programs
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): isaacs is the npm creator with a long legitimate track record; no keywords/deps are expected for this minimal utility. SPAM-FLAGGED is a false positive for this well-known author. | ai | |
| provenance | publisher-changed | AI (provenance): npm/read is an official npm org package; transition from npm-cli-ops to GitHub Actions CI publishing is a documented security improvement, not a compromise signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers (fritzy, lukekarrys, isaacs) reflect normal npm org team rotation; not indicative of takeover given SLSA provenance and official repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy reflects a major version rewrite (v3→v5, TypeScript/ESM migration); SLSA provenance confirms legitimate CI publish from official npm org repo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (reggi, hashtagchris, owlstronaut) are known npm/GitHub org contributors; routine team rotation for an npm-owned package. | ai | |
| dependencies | unvetted-dep:mute-stream | AI (dependencies): `mute-stream` is a well-known npm CLI utility maintained by the same npm team; its use in `read` for terminal input masking is expected and stable. | ai | |
| typosquat | typosquat.levenshtein:react | AI (typosquat): 'read' is a generic Unix utility name with no intent to impersonate 'react'; already marked accepted risk. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 1 / 7 | |
| 5.0.1 | 1 / 11 | |
| 5.0.0 | 1 / 11 | |
| 4.1.0 | 1 / 11 | |
| 4.0.0 | 1 / 11 | |
| 3.0.1 | 1 / 11 | |
| 3.0.0 | 1 / 11 | |
| 2.1.0 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.0.7 | 1 / 1 | |
| 1.0.6 | 1 / 1 | |
| 1.0.5 | 1 / 1 | |
| 1.0.4 | 1 / 1 | |
| 1.0.3 | 1 / 1 | |
| 1.0.2 | 1 / 1 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 | |
| 0.1.1 | 0 / 1 | |
| 0.1.0 | 0 / 1 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-22. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-11-18. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-13. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-12-13. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.