@mjsz-vbr-elements/core
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/TimezoneSelector-WKm_DaDH.js | AI (source-diff): Vite-minified dist output; long lines are normal for this build pipeline, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/TimezoneSelector-T8Y8aFc-.js | AI (source-diff): Vite-bundled Vue component output; long lines are minification artifacts, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/TimezoneSelector-qP6OxXMD.js | AI (source-diff): Standard Vite-bundled ESM output; long lines are minification artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/TimezoneSelector-DKtwSWAw.js | AI (source-diff): Vite-bundled ESM output; long lines are minified Vue component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/TimezoneSelector-CRy1AyTX.js | AI (source-diff): Vite build output with readable imports and package banner; minification is expected for this build toolchain. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package with 190 versions and SLSA provenance; sparse README/keywords are cosmetic, not a risk signal. | ai | |
| dependencies | unvetted-dep:@lostui/utils | AI (dependencies): Dependency is also flagged as phantom (not directly imported); low actual risk for this established package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package for MJSZ VBR widgets; 'core' suffix is unrelated to the 'cors' npm package. | ai | |
| phantom-deps | phantom-dep:@mjsz-vbr-elements/shared | AI (phantom-deps): Same-org sibling package in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Monorepo package; deps referenced in config/build files, stable false positive. | ai | |
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): Monorepo package; deps referenced in config/build files, stable false positive. | ai | |
| phantom-deps | phantom-dep:@xstate/fsm | AI (phantom-deps): Monorepo package; deps referenced in config/build files, stable false positive. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Monorepo package; deps referenced in config/build files, stable false positive. | ai | |
| phantom-deps | phantom-dep:@lostui/utils | AI (phantom-deps): Monorepo package; deps referenced in config/build files, stable false positive. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Monorepo package; deps referenced in config/build files, stable false positive. | ai |
Versions (showing 28 of 128)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 8 / 4 | |
| 2.4.0 | 8 / 4 | |
| 2.3.8 | 7 / 4 | |
| 2.3.7 | 7 / 4 | |
| 2.3.6 | 7 / 4 | |
| 2.3.5 | 7 / 4 | |
| 2.3.4 | 7 / 4 | |
| 2.3.3 | 7 / 4 | |
| 2.3.2 | 7 / 4 | |
| 2.3.1 | 7 / 4 | |
| 2.3.0 | 7 / 4 | |
| 2.2.7 | 7 / 4 | |
| 2.2.6 | 7 / 4 | |
| 2.2.5 | 7 / 4 | |
| 2.2.4 | 7 / 4 | |
| 2.2.3 | 7 / 4 | |
| 2.2.2 | 7 / 4 | |
| 2.2.1 | 7 / 4 | |
| 2.2.0 | 7 / 4 | |
| 2.1.10 | 7 / 5 | |
| 2.1.9 | 7 / 5 | |
| 2.1.8 | 7 / 5 | |
| 2.1.7 | 7 / 5 | |
| 2.1.6 | 7 / 5 | |
| 2.1.5 | 7 / 5 | |
| 2.1.4 | 7 / 5 | |
| 2.1.2 | 7 / 5 | |
| 2.1.0 | 7 / 5 |
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.
v2.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.