@vitessce/zarr-utils
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from keller-mark to GitHub Actions CI/CD is a legitimate automation change, backed by SLSA provenance attestation. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a Proxy trap for zarr dtype adaptation — idiomatic JS, not obfuscation. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 3 / 1 | |
| 4.0.0 | 3 / 1 | |
| 3.9.11 | 3 / 1 | |
| 3.9.10 | 3 / 1 | |
| 3.9.9 | 3 / 1 | |
| 3.9.8 | 3 / 1 | |
| 3.9.7 | 3 / 1 | |
| 3.9.6 | 3 / 1 | |
| 3.9.5 | 3 / 1 | |
| 3.9.4 | 3 / 1 | |
| 3.9.3 | 3 / 1 | |
| 3.9.2 | 3 / 1 | |
| 3.9.1 | 3 / 1 | |
| 3.9.0 | 3 / 1 | |
| 3.8.13 | 3 / 1 | |
| 3.8.10 | 3 / 1 | |
| 3.8.9 | 3 / 1 | |
| 3.8.8 | 3 / 1 | |
| 3.8.7 | 3 / 1 | |
| 3.8.6 | 3 / 1 | |
| 3.8.5 | 3 / 1 | |
| 3.8.4 | 3 / 1 | |
| 3.8.3 | 3 / 1 | |
| 3.8.2 | 3 / 1 | |
| 3.8.1 | 3 / 1 | |
| 3.8.0 | 3 / 1 | |
| 3.7.1 | 3 / 1 | |
| 3.7.0 | 3 / 1 | |
| 3.6.18 | 3 / 1 | |
| 3.6.17 | 3 / 1 | |
| 3.6.16 | 3 / 1 | |
| 3.6.15 | 3 / 1 | |
| 3.6.14 | 3 / 0 | |
| 3.6.13 | 3 / 0 | |
| 3.6.12 | 3 / 0 | |
| 3.6.11 | 3 / 0 | |
| 3.6.10 | 3 / 0 | |
| 3.6.9 | 3 / 0 | |
| 3.6.8 | 3 / 0 | |
| 3.6.7 | 3 / 0 | |
| 3.6.6 | 3 / 0 | |
| 3.6.5 | 3 / 0 | |
| 3.6.4 | 3 / 0 | |
| 3.6.3 | 3 / 0 | |
| 3.6.2 | 3 / 0 | |
| 3.6.1 | 3 / 0 | |
| 3.6.0 | 3 / 0 | |
| 3.5.12 | 3 / 0 | |
| 3.5.11 | 3 / 0 | |
| 3.5.10 | 3 / 0 | |
| 3.5.9 | 3 / 0 |
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.