@novasamatech/tr-ui
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/components/context-menu.js | AI (source-diff): Bundled vite output; sample shows readable Tailwind/Radix code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/components/empty.js | AI (source-diff): Standard Vite minified component bundle; readable React/CVA code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/components/list-item.js | AI (source-diff): Standard Vite minified component bundle; readable React/CVA code, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:next-themes | AI (phantom-deps): next-themes is a declared runtime dep used via config/CSS; phantom-dep heuristic false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:@fontsource/inter | AI (phantom-deps): @fontsource/inter is a CSS font package imported via config, not JS imports; phantom-dep heuristic false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.2.13 | 24 / 39 | |
| 0.2.12 | 24 / 39 | |
| 0.2.11 | 23 / 39 | |
| 0.2.10 | 23 / 39 | |
| 0.2.9 | 23 / 39 | |
| 0.2.8 | 23 / 39 | |
| 0.2.7 | 23 / 39 | |
| 0.2.6 | 23 / 39 | |
| 0.2.5 | 23 / 39 | |
| 0.2.4 | 23 / 39 | |
| 0.2.3 | 23 / 39 | |
| 0.2.2 | 23 / 39 | |
| 0.2.1 | 23 / 39 | |
| 0.2.0 | 23 / 39 | |
| 0.1.38 | 23 / 39 | |
| 0.1.37 | 22 / 39 | |
| 0.1.36 | 21 / 41 | |
| 0.1.35 | 21 / 41 | |
| 0.1.34 | 20 / 41 | |
| 0.1.33 | 20 / 41 | |
| 0.1.32 | 20 / 41 |
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yanaty) than the most recent previously approved version (kalininilya) on 2026-05-06, but yanaty 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.
v0.2.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (johnthecat) than the most recent previously approved version (kalininilya) on 2026-05-01, but johnthecat 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.