strtok3
A promise based streaming tokenizer
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:then-read-stream | AI (dependencies): then-read-stream is authored by the same maintainer (Borewit) and is a natural dependency for a streaming tokenizer; not a risk for this package. | ai | |
| phantom-deps | phantom-dep:es6-promise | AI (phantom-deps): es6-promise is a declared runtime dependency used as a polyfill; not being directly imported is expected for this type of dependency. No security concern. | ai | |
| provenance | no-provenance | AI (provenance): Package is 3223 days old; provenance attestation was not standard practice at publish time. Publisher has a strong track record with 61 approved packages. | ai |
Versions (showing 3 of 103)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 4 / 17 | |
| 0.0.1 | 4 / 17 | |
| 7.0.0-alpha.4 | 2 / 22 |
v0.1.1
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0-alpha.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.