@vitessce/layer-controller
10
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
keller-mark
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 sub-package; missing description is a consistent pattern across the vitessce package family, not a malware indicator. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.9.11 | 9 / 4 | |
| 3.9.10 | 9 / 4 | |
| 3.9.9 | 9 / 4 | |
| 3.9.8 | 9 / 4 | |
| 3.9.7 | 9 / 4 | |
| 3.8.10 | 9 / 4 | |
| 3.8.9 | 9 / 4 | |
| 3.8.8 | 9 / 4 | |
| 3.8.7 | 9 / 4 | |
| 3.8.6 | 9 / 4 |
v3.8.10
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.9
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.8
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.7
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.6
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.