@gmod/vcf
High performance streaming Variant Call Format (VCF) parser in pure JavaScript
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.0.9 | 0 / 15 | |
| 7.0.8 | 0 / 15 | |
| 7.0.7 | 0 / 15 | |
| 7.0.5 | 0 / 15 | |
| 7.0.4 | 0 / 15 | |
| 7.0.3 | 0 / 15 | |
| 7.0.2 | 0 / 15 | |
| 7.0.1 | 0 / 15 | |
| 7.0.0 | 0 / 16 | |
| 6.1.2 | 0 / 16 | |
| 6.1.1 | 0 / 16 | |
| 6.1.0 | 0 / 16 |
v7.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.