@mks2508/mks-ui
UI component library - Shadcn/Animate UI based with DevEnv components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/react-ui/index.js | AI (source-diff): File is a readable ESM barrel export; long lines are from bundled output, not obfuscation. | ai | |
| dependencies | unvetted-dep:@base-ui-components/react | AI (dependencies): @base-ui-components/react is a legitimate MUI Base UI package; stable false positive for this library. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Personal scoped UI library; no repo link is a style issue, not malicious. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/vite | AI (phantom-deps): Vite plugin for Tailwind; config-only reference is expected. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Tailwind is a build-time CSS tool; referenced in config files is expected for a UI component library. | ai | |
| phantom-deps | phantom-dep:@fontsource-variable/geist-mono | AI (phantom-deps): Font package referenced in CSS/config; not directly imported in JS is expected. | ai | |
| phantom-deps | phantom-dep:shadcn | AI (phantom-deps): shadcn is a CLI/build tool; config-only reference is expected for this type of library. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): CSS animation utility; config-only reference is normal for a Tailwind-based UI library. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 12 / 24 | |
| 0.8.2 | 12 / 24 | |
| 0.8.1 | 12 / 24 | |
| 0.8.0 | 12 / 24 | |
| 0.7.0 | 12 / 24 | |
| 0.6.8 | 12 / 24 | |
| 0.6.7 | 12 / 24 | |
| 0.6.6 | 12 / 24 | |
| 0.6.5 | 12 / 24 | |
| 0.6.4 | 12 / 24 | |
| 0.6.3 | 12 / 24 | |
| 0.6.2 | 12 / 24 | |
| 0.6.1 | 12 / 24 | |
| 0.6.0 | 12 / 24 | |
| 0.5.8 | 12 / 24 | |
| 0.5.7 | 12 / 24 | |
| 0.5.4 | 12 / 24 | |
| 0.5.2 | 12 / 24 | |
| 0.5.1 | 12 / 24 | |
| 0.5.0 | 12 / 24 | |
| 0.4.0 | 12 / 24 | |
| 0.3.2 | 12 / 15 | |
| 0.3.1 | 12 / 15 | |
| 0.2.1 | 12 / 15 | |
| 0.2.0 | 12 / 15 | |
| 0.1.1 | 14 / 13 |
v0.4.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.
v0.3.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.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mks2508.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.