@vitessce/tooltip
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 human publisher to GitHub Actions CI/CD with SLSA attestation; consistent with legitimate automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-backed publish with SLSA provenance; no malicious indicators present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a consistent pattern across the vitessce package family, not a malice indicator. | ai |
Versions (showing 74 of 74)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 3 / 3 | |
| 4.0.0 | 3 / 3 | |
| 3.9.11 | 3 / 3 | |
| 3.9.10 | 3 / 3 | |
| 3.9.9 | 3 / 3 | |
| 3.9.8 | 3 / 3 | |
| 3.9.7 | 3 / 3 | |
| 3.9.6 | 3 / 3 | |
| 3.9.5 | 3 / 3 | |
| 3.9.4 | 3 / 3 | |
| 3.9.3 | 3 / 3 | |
| 3.9.2 | 3 / 3 | |
| 3.9.1 | 3 / 3 | |
| 3.9.0 | 3 / 3 | |
| 3.8.13 | 3 / 3 | |
| 3.8.10 | 3 / 3 | |
| 3.8.9 | 3 / 3 | |
| 3.8.8 | 3 / 3 | |
| 3.8.7 | 3 / 3 | |
| 3.8.6 | 3 / 3 | |
| 3.8.5 | 3 / 3 | |
| 3.8.4 | 3 / 3 | |
| 3.8.3 | 3 / 3 | |
| 3.8.2 | 3 / 3 | |
| 3.8.1 | 3 / 3 | |
| 3.8.0 | 3 / 3 | |
| 3.7.1 | 3 / 3 | |
| 3.7.0 | 3 / 3 | |
| 3.6.18 | 3 / 3 | |
| 3.6.17 | 3 / 3 | |
| 3.6.16 | 3 / 3 | |
| 3.6.15 | 3 / 3 | |
| 3.6.14 | 3 / 3 | |
| 3.6.13 | 3 / 3 | |
| 3.6.12 | 3 / 3 | |
| 3.6.11 | 3 / 3 | |
| 3.6.10 | 3 / 3 | |
| 3.6.9 | 3 / 3 | |
| 3.6.8 | 3 / 3 | |
| 3.6.7 | 3 / 3 | |
| 3.6.6 | 3 / 3 | |
| 3.6.5 | 3 / 3 | |
| 3.6.4 | 3 / 3 | |
| 3.6.3 | 3 / 3 | |
| 3.6.2 | 3 / 3 | |
| 3.6.1 | 3 / 3 | |
| 3.6.0 | 3 / 3 | |
| 3.5.12 | 3 / 3 | |
| 3.5.11 | 3 / 3 | |
| 3.5.10 | 3 / 3 | |
| 3.5.9 | 3 / 3 | |
| 3.5.8 | 3 / 3 | |
| 3.5.7 | 3 / 3 | |
| 3.5.6 | 3 / 3 | |
| 3.5.5 | 3 / 3 | |
| 3.5.4 | 3 / 3 | |
| 3.5.3 | 3 / 3 | |
| 3.5.2 | 2 / 3 | |
| 3.5.1 | 2 / 3 | |
| 3.5.0 | 2 / 3 | |
| 3.4.14 | 2 / 3 | |
| 3.4.12 | 2 / 3 | |
| 3.4.11 | 2 / 3 | |
| 3.4.10 | 2 / 3 | |
| 3.4.9 | 2 / 3 | |
| 3.4.8 | 2 / 3 | |
| 3.4.7 | 2 / 3 | |
| 3.4.6 | 2 / 3 | |
| 3.4.5 | 2 / 3 | |
| 3.4.4 | 2 / 3 | |
| 3.4.3 | 2 / 3 | |
| 3.4.2 | 2 / 3 | |
| 3.4.1 | 2 / 3 | |
| 3.4.0 | 2 / 3 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.