@gmod/bed
A BED file format parser with autoSql support
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @gmod/bed is a genomics BED format parser; name similarity to 'zod' is coincidental, not a typosquat. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.2.5 | 0 / 12 | |
| 2.2.3 | 0 / 12 | |
| 2.2.2 | 0 / 14 | |
| 2.2.1 | 0 / 14 | |
| 2.2.0 | 0 / 14 | |
| 2.1.10 | 0 / 12 | |
| 2.1.9 | 0 / 12 | |
| 2.1.8 | 0 / 12 | |
| 2.1.7 | 0 / 11 | |
| 2.1.5 | 0 / 11 | |
| 2.1.4 | 0 / 11 |
v2.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.