@primeuix/themes
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/aura-compat/index.mjs | AI (source-diff): tsup-minified token module. | ai | |
| source-diff | obfuscated-file:umd/aura-compat.js | AI (source-diff): Minified theme-token bundle output, not obfuscation; stable for this build. | ai | |
| source-diff | obfuscated-file:umd/lara-compat.js | AI (source-diff): Minified theme-token bundle output. | ai | |
| source-diff | obfuscated-file:umd/material-compat.js | AI (source-diff): Minified theme-token bundle output. | ai | |
| source-diff | obfuscated-file:umd/nora-compat.js | AI (source-diff): Minified theme-token bundle output. | ai | |
| source-diff | obfuscated-file:dist/aura-compat/autocomplete/index.mjs | AI (source-diff): tsup-minified token module. | ai | |
| source-diff | obfuscated-file:dist/aura-compat/base/index.mjs | AI (source-diff): tsup-minified token module. | ai | |
| source-diff | obfuscated-file:dist/aura-compat/button/index.mjs | AI (source-diff): tsup-minified token module. | ai | |
| source-diff | obfuscated-file:dist/aura-compat/datatable/index.mjs | AI (source-diff): tsup-minified token module. | ai | |
| source-diff | obfuscated-file:dist/aura-compat/datepicker/index.mjs | AI (source-diff): tsup-minified token module. | ai | |
| provenance | no-provenance | AI (provenance): Established PrimeTek org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 1 / 0 | |
| 2.0.3 | 1 / 0 | |
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 |
v3.0.0
12 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mert.sincan) than the most recent previously approved version (cagatay.civici) on 2026-07-15, but mert.sincan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.