@vitessce/genomic-profiles
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo internal package; missing description is stable and not indicative of malice. | ai | |
| dependencies | unvetted-dep:higlass | AI (dependencies): HiGlass is a well-known genomic visualization library; expected dependency for this genomic-profiles package. | ai | |
| dependencies | unvetted-dep:higlass-zarr-datafetchers | AI (dependencies): HiGlass ecosystem data fetcher; consistent with this package's genomic visualization purpose. | ai | |
| phantom-deps | phantom-dep:@vitessce/utils | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.9.11 | 9 / 3 | |
| 3.9.10 | 9 / 3 | |
| 3.9.9 | 9 / 3 | |
| 3.9.8 | 9 / 3 | |
| 3.9.7 | 9 / 3 | |
| 3.8.13 | 9 / 3 | |
| 3.8.10 | 9 / 3 | |
| 3.8.9 | 9 / 3 | |
| 3.8.8 | 9 / 3 | |
| 3.8.7 | 9 / 3 | |
| 3.8.6 | 9 / 3 |
v3.8.13
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2025-12-14, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.