@tanstack/match-sorter-utils
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 | missing-githead | AI (provenance): Benign publish-environment metadata change, no behavior impact for this trusted publisher. | ai | |
| phantom-deps | phantom-dep:remove-accents | AI (phantom-deps): Legitimate dep used for accent stripping; likely missed by import scan due to build structure. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 8.19.4 | 1 / 0 | |
| 8.15.1 | 1 / 0 | |
| 8.11.8 | 1 / 0 | |
| 8.11.7 | 1 / 0 | |
| 8.11.3 | 1 / 0 | |
| 8.8.4 | 1 / 0 | |
| 8.7.6 | 1 / 0 | |
| 8.7.2 | 1 / 0 | |
| 8.7.0 | 1 / 0 | |
| 8.5.14 | 1 / 0 | |
| 8.1.1 | 1 / 0 | |
| 8.0.13 | 1 / 0 | |
| 8.0.12 | 1 / 0 | |
| 8.0.11 | 1 / 0 | |
| 8.0.8 | 1 / 0 | |
| 8.0.7 | 1 / 0 | |
| 8.0.6 | 1 / 0 | |
| 8.0.4 | 1 / 0 | |
| 8.0.3 | 1 / 0 | |
| 8.0.0 | 1 / 0 |
v8.15.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.