cidr-regex
Regular expression for matching IP addresses in CIDR notation
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 manual publish (silverwind) to GitHub Actions CI/CD with SLSA provenance. Legitimate automation of publishing for this package. | ai | |
| provenance | missing-githead | AI (provenance): Expected side effect of switching to GitHub Actions publishing; gitHead is not set by CI/CD workflows. SLSA provenance compensates. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 14 | |
| 5.0.5 | 0 / 14 | |
| 5.0.4 | 0 / 14 | |
| 5.0.3 | 0 / 14 | |
| 5.0.2 | 1 / 12 | |
| 5.0.1 | 1 / 11 | |
| 5.0.0 | 1 / 11 | |
| 4.1.3 | 1 / 12 | |
| 4.1.2 | 1 / 12 | |
| 4.1.1 | 1 / 13 | |
| 4.1.0 | 1 / 14 | |
| 4.0.5 | 1 / 7 | |
| 4.0.4 | 1 / 7 | |
| 4.0.3 | 1 / 6 | |
| 4.0.2 | 1 / 7 | |
| 4.0.1 | 1 / 6 | |
| 4.0.0 | 1 / 6 | |
| 3.1.1 | 1 / 6 | |
| 3.1.0 | 1 / 6 | |
| 3.0.0 | 1 / 5 | |
| 2.0.10 | 1 / 4 | |
| 2.0.9 | 1 / 4 | |
| 2.0.8 | 1 / 4 | |
| 2.0.7 | 1 / 3 | |
| 2.0.6 | 1 / 3 | |
| 2.0.5 | 1 / 3 | |
| 2.0.4 | 1 / 3 | |
| 2.0.3 | 1 / 3 | |
| 2.0.2 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.0.7 | 0 / 14 | |
| 1.0.6 | 0 / 4 | |
| 1.0.5 | 0 / 4 | |
| 1.0.2 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v6.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v5.0.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v5.0.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-09. 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.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.