cr
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
jonschlinkert
Keywords
carriagecarriage-returnfilefsnewlinenewlinesnlnormalizereturnreturnsstring
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): cr is a legitimate carriage-return utility by trusted publisher jonschlinkert; short name proximity to 'pg' is coincidental and not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): cr is a legitimate carriage-return utility; Levenshtein proximity to 'cors' is coincidental for this short-named package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): cr is a legitimate carriage-return utility; Levenshtein proximity to 'qs' is coincidental for this short-named package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 0 / 1 |
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.