match-sorter
Simple, expected, and deterministic best-match sorting of an array in JavaScript
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): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance attestation; matches common pattern for kentcdodds packages. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is injected by Babel's transform-runtime plugin; not directly imported but correctly declared as a dependency. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 8.3.0 | 2 / 3 | |
| 8.2.0 | 2 / 3 | |
| 8.1.0 | 2 / 3 | |
| 8.0.3 | 2 / 3 | |
| 8.0.2 | 2 / 3 | |
| 8.0.1 | 2 / 3 | |
| 8.0.0 | 2 / 3 | |
| 7.0.0 | 2 / 3 | |
| 6.4.0 | 2 / 3 | |
| 6.3.4 | 2 / 3 | |
| 6.3.3 | 2 / 3 | |
| 6.3.2 | 2 / 3 | |
| 6.3.1 | 2 / 3 | |
| 6.3.0 | 2 / 3 | |
| 6.2.0 | 2 / 3 | |
| 6.1.0 | 2 / 3 | |
| 6.0.2 | 2 / 3 | |
| 6.0.1 | 2 / 4 | |
| 6.0.0 | 2 / 4 | |
| 5.0.0 | 2 / 1 | |
| 4.2.1 | 2 / 1 | |
| 4.2.0 | 2 / 1 | |
| 4.1.0 | 2 / 1 | |
| 4.0.2 | 2 / 1 | |
| 4.0.1 | 2 / 1 | |
| 4.0.0 | 1 / 1 | |
| 3.1.1 | 1 / 1 | |
| 3.1.0 | 1 / 1 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 1 / 1 | |
| 2.3.0 | 1 / 1 | |
| 2.2.3 | 1 / 1 | |
| 2.2.2 | 1 / 1 | |
| 2.2.1 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.8.1 | 2 / 25 | |
| 1.8.0 | 2 / 25 | |
| 1.7.0 | 2 / 25 | |
| 1.6.0 | 2 / 24 | |
| 1.5.0 | 2 / 24 | |
| 1.4.1 | 2 / 26 | |
| 1.4.0 | 1 / 25 | |
| 1.3.0 | 0 / 21 | |
| 1.2.1 | 0 / 21 | |
| 1.2.0 | 0 / 21 | |
| 1.1.0 | 0 / 21 | |
| 1.0.0 | 0 / 21 |
v8.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-24. 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.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.