@mjsz-vbr-elements/gamecenter
Data visualization for MJSZ VBR
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Bundled Vue component package; deps may be consumed indirectly via build output rather than direct imports. | ai | |
| phantom-deps | phantom-dep:@mjsz-vbr-elements/shared | AI (phantom-deps): Same-org sibling package; likely consumed via build tooling or re-exports, stable false positive. | ai |
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 2.46.0 | 4 / 5 | |
| 2.45.1 | 4 / 5 | |
| 2.45.0 | 4 / 5 | |
| 2.44.0 | 4 / 5 | |
| 2.43.2 | 4 / 5 | |
| 2.43.1 | 4 / 5 | |
| 2.43.0 | 4 / 5 | |
| 2.42.0 | 4 / 5 | |
| 2.41.0 | 4 / 5 | |
| 2.40.5 | 4 / 5 | |
| 2.40.4 | 4 / 5 | |
| 2.40.3 | 4 / 5 | |
| 2.40.2 | 4 / 5 | |
| 2.40.1 | 4 / 5 | |
| 2.40.0 | 4 / 5 | |
| 2.39.1 | 4 / 5 | |
| 2.39.0 | 4 / 5 | |
| 2.38.4 | 4 / 5 | |
| 2.38.3 | 4 / 5 | |
| 2.38.2 | 4 / 5 | |
| 2.38.1 | 4 / 5 | |
| 2.38.0 | 4 / 5 | |
| 2.37.0 | 4 / 5 | |
| 2.36.0 | 4 / 5 | |
| 2.35.1 | 4 / 5 | |
| 2.35.0 | 4 / 5 | |
| 2.34.1 | 4 / 5 | |
| 2.34.0 | 4 / 5 | |
| 2.33.2 | 4 / 5 | |
| 2.33.1 | 4 / 5 | |
| 2.33.0 | 4 / 5 | |
| 2.32.0 | 4 / 5 | |
| 2.31.2 | 4 / 5 | |
| 2.31.1 | 4 / 5 | |
| 2.31.0 | 4 / 5 | |
| 2.30.2 | 5 / 5 | |
| 2.30.1 | 5 / 5 | |
| 2.30.0 | 5 / 5 | |
| 2.29.3 | 5 / 5 | |
| 2.29.2 | 5 / 5 | |
| 2.29.1 | 5 / 5 | |
| 2.29.0 | 5 / 5 | |
| 2.28.0 | 5 / 5 | |
| 2.27.0 | 5 / 5 | |
| 2.26.6 | 5 / 5 | |
| 2.26.5 | 5 / 5 | |
| 2.26.4 | 5 / 5 | |
| 2.26.3 | 5 / 5 | |
| 2.26.2 | 5 / 5 | |
| 2.26.1 | 5 / 5 | |
| 2.26.0 | 5 / 5 | |
| 2.25.3 | 5 / 5 | |
| 2.25.2 | 5 / 5 | |
| 2.25.1 | 5 / 5 | |
| 2.25.0 | 5 / 5 | |
| 2.24.1 | 5 / 5 | |
| 2.24.0 | 5 / 5 | |
| 2.23.3 | 5 / 5 | |
| 2.23.2 | 5 / 5 | |
| 2.23.1 | 5 / 5 | |
| 2.23.0 | 5 / 5 | |
| 2.22.2 | 5 / 5 | |
| 2.22.1 | 5 / 5 | |
| 2.22.0 | 5 / 5 | |
| 2.21.1 | 5 / 5 | |
| 2.21.0 | 5 / 5 | |
| 2.20.1 | 5 / 5 | |
| 2.20.0 | 5 / 5 | |
| 2.19.2 | 5 / 5 | |
| 2.19.1 | 5 / 5 | |
| 2.19.0 | 5 / 5 | |
| 2.18.0 | 5 / 5 | |
| 2.17.0 | 5 / 5 | |
| 2.16.0 | 5 / 5 | |
| 2.15.0 | 5 / 5 | |
| 2.14.5 | 5 / 5 | |
| 2.14.4 | 5 / 5 | |
| 2.14.3 | 5 / 5 | |
| 2.14.1 | 5 / 5 | |
| 2.14.0 | 5 / 5 | |
| 2.13.1 | 5 / 5 | |
| 2.13.0 | 5 / 5 | |
| 2.12.0 | 5 / 5 | |
| 2.11.3 | 5 / 4 | |
| 2.11.2 | 5 / 4 | |
| 2.11.1 | 5 / 4 | |
| 2.11.0 | 5 / 4 | |
| 2.10.0 | 5 / 4 | |
| 2.9.1 | 5 / 4 | |
| 2.9.0 | 5 / 4 | |
| 2.8.0 | 5 / 4 | |
| 2.7.2 | 5 / 4 | |
| 2.7.1 | 5 / 4 | |
| 2.7.0 | 5 / 4 | |
| 2.6.4 | 5 / 4 | |
| 2.6.3 | 5 / 4 | |
| 2.6.2 | 5 / 4 | |
| 2.6.1 | 5 / 4 | |
| 2.6.0 | 5 / 4 | |
| 2.5.2 | 5 / 4 |
v2.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.45.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.