ranges-sort
Sort string index ranges
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD with SLSA provenance; expected for codsen monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): codsen monorepo has 145+ utility packages by design; no-deps is normal for this leaf package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.1.3 | 0 / 0 | |
| 6.1.0 | 0 / 0 | |
| 6.0.25 | 0 / 0 | |
| 6.0.24 | 0 / 0 | |
| 6.0.23 | 0 / 0 | |
| 6.0.14 | 0 / 0 |
v6.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.25
2 findingsThis version was published by a different npm account than previous versions on 2025-10-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.24
2 findingsThis version was published by a different npm account than previous versions on 2025-10-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.23
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.