co-read
Consume a readable stream generator-style
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 4614 days old from a highly trusted publisher (juliangruber); 0.0.0 versioning reflects early npm era conventions, not malicious intent. | ai | |
| provenance | missing-githead | AI (provenance): Package is 4614 days old from a highly trusted publisher (juliangruber). Missing gitHead reflects a historical publish environment change, not a supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance attestation practices; no provenance is expected for this era of publishing. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): stream-read is a juliangruber package consistent with his stream utility ecosystem; the dep swap from debug to stream-read is a legitimate refactor. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 | |
| 0.0.0 | 0 / 4 |
v0.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: juliangruber.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.