ranges-push
Gather string index ranges
3
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
royston
Keywords
deletefrommanymultiplerangesreplacesliceslicessplicestring
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ranges-sort | AI (phantom-deps): Sibling codsen monorepo package; phantom-dep finding reflects monorepo build config references, not a real import gap. Stable for this package. | ai | |
| phantom-deps | phantom-dep:codsen-utils | AI (phantom-deps): Sibling codsen monorepo package; phantom-dep finding reflects monorepo build config references, not a real import gap. Stable for this package. | ai | |
| phantom-deps | phantom-dep:string-trim-spaces-only | AI (phantom-deps): Sibling codsen monorepo package; phantom-dep finding reflects monorepo build config references, not a real import gap. Stable for this package. | ai | |
| phantom-deps | phantom-dep:string-collapse-leading-whitespace | AI (phantom-deps): Sibling codsen monorepo package; phantom-dep finding reflects monorepo build config references, not a real import gap. Stable for this package. | ai |
v7.1.3
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.28
2 findings
HIGH
Publisher changed: royston → GitHub Actions (on 2025-10-07)
provenance
This version was published by a different npm account than previous versions on 2025-10-07. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.19
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.