oxc-walker
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:magic-regexp | AI (dependencies): magic-regexp is a legitimate, well-known regex utility library; the unvetted flag is a registry gap, not a security concern for this package. | ai | |
| dependencies | unvetted-peer-dep:oxc-parser | AI (dependencies): oxc-parser is from the same oxc-project ecosystem as oxc-walker; the peer dep relationship is expected and legitimate. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 1 / 12 | |
| 0.7.0 | 1 / 11 | |
| 0.6.0 | 1 / 11 | |
| 0.5.0 | 1 / 12 | |
| 0.4.0 | 2 / 13 | |
| 0.3.0 | 2 / 13 |
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.