@mjsz-vbr-elements/elements
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:@mjsz-vbr-elements/shared | AI (phantom-deps): Same-org monorepo sibling; bundled at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Peer/transitive dep consumed via bundled output; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate component library in active monorepo; sparse README is a style choice, not spam. | ai |
Versions (showing 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 2.5.1 | 5 / 4 | |
| 2.5.0 | 5 / 4 | |
| 2.4.3 | 5 / 4 | |
| 2.4.2 | 5 / 4 | |
| 2.4.1 | 5 / 4 | |
| 2.4.0 | 5 / 4 | |
| 2.3.8 | 5 / 4 |
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.