@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 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 2.45.1 | 8 / 4 | |
| 2.45.0 | 8 / 4 | |
| 2.44.0 | 8 / 4 | |
| 2.43.2 | 8 / 4 | |
| 2.43.1 | 8 / 4 | |
| 2.42.0 | 8 / 4 | |
| 2.41.0 | 8 / 4 | |
| 2.40.5 | 8 / 4 | |
| 2.40.4 | 8 / 4 | |
| 2.40.3 | 8 / 4 | |
| 2.40.2 | 8 / 4 | |
| 2.40.0 | 8 / 4 | |
| 2.39.0 | 8 / 4 | |
| 2.38.4 | 8 / 4 | |
| 2.38.3 | 8 / 4 | |
| 2.38.2 | 8 / 4 | |
| 2.38.1 | 8 / 4 | |
| 2.38.0 | 8 / 4 | |
| 2.37.0 | 8 / 4 | |
| 2.36.0 | 8 / 4 | |
| 2.35.1 | 8 / 4 | |
| 2.35.0 | 8 / 4 | |
| 2.34.1 | 8 / 4 | |
| 2.33.2 | 8 / 4 | |
| 2.33.1 | 8 / 4 | |
| 2.33.0 | 8 / 4 | |
| 2.32.0 | 8 / 4 | |
| 2.31.2 | 8 / 4 | |
| 2.31.1 | 8 / 4 | |
| 2.31.0 | 8 / 4 | |
| 2.30.2 | 8 / 4 | |
| 2.30.1 | 8 / 4 | |
| 2.30.0 | 8 / 4 | |
| 2.29.3 | 8 / 4 | |
| 2.29.2 | 8 / 4 | |
| 2.29.1 | 8 / 4 | |
| 2.29.0 | 8 / 4 | |
| 2.28.0 | 8 / 4 | |
| 2.27.0 | 8 / 4 | |
| 2.26.6 | 8 / 4 | |
| 2.26.5 | 8 / 4 | |
| 2.26.4 | 8 / 4 | |
| 2.26.3 | 8 / 4 | |
| 2.26.2 | 8 / 4 | |
| 2.26.1 | 8 / 4 | |
| 2.26.0 | 8 / 4 | |
| 2.25.3 | 8 / 4 | |
| 2.25.2 | 8 / 4 | |
| 2.25.1 | 8 / 4 | |
| 2.25.0 | 8 / 4 | |
| 2.24.1 | 8 / 4 |
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.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.44.0
2 findingsPackage name '@mjsz-vbr-elements/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.43.2
2 findingsPackage name '@mjsz-vbr-elements/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.43.1
2 findingsPackage name '@mjsz-vbr-elements/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.42.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.41.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.40.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.40.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.40.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.40.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.40.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.38.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.38.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.38.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.38.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.36.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.35.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.34.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.