@tanstack/cta-ui
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/assets/index-16uOszEx.js | AI (source-diff): Standard Vite-minified React bundle for a UI package; not obfuscated, just minified frontend output. | ai | |
| source-diff | obfuscated-file:dist/assets/index-nLTGZwWC.js | AI (source-diff): Standard Vite minified bundle for a React UI package; not obfuscated, readable code with license headers. | ai | |
| source-diff | obfuscated-file:dist/assets/index-dikOiXwx.js | AI (source-diff): Standard Vite-minified React bundle with accompanying source map; expected artifact for this UI package. | ai | |
| source-diff | obfuscated-file:dist/assets/index-CV3P_WqJ.js | AI (source-diff): Standard Vite-minified UI bundle for a React component library; not obfuscation. | ai | |
| phantom-deps | phantom-dep:next-themes | AI (phantom-deps): UI peer dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Tailwind utility referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Tailwind plugin referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React is a peer/config dependency for a UI package; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Used in config/build tooling context; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:sonner | AI (phantom-deps): UI peer dependency referenced in config; stable false positive for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.48.2 | 15 / 15 | |
| 0.28.0 | 15 / 15 | |
| 0.27.1 | 15 / 15 | |
| 0.27.0 | 15 / 15 | |
| 0.26.1 | 15 / 15 | |
| 0.26.0 | 15 / 15 | |
| 0.25.2 | 15 / 15 | |
| 0.25.1 | 15 / 15 | |
| 0.25.0 | 15 / 15 | |
| 0.24.1 | 15 / 15 | |
| 0.24.0 | 15 / 15 | |
| 0.23.2 | 15 / 15 | |
| 0.23.1 | 15 / 15 | |
| 0.23.0 | 15 / 15 | |
| 0.22.3 | 15 / 15 | |
| 0.22.2 | 15 / 15 | |
| 0.22.1 | 15 / 15 | |
| 0.22.0 | 15 / 15 | |
| 0.21.0 | 15 / 15 | |
| 0.20.0 | 15 / 15 | |
| 0.19.0 | 15 / 15 | |
| 0.17.5 | 15 / 15 | |
| 0.17.4 | 15 / 15 | |
| 0.17.3 | 15 / 15 | |
| 0.17.2 | 15 / 15 | |
| 0.17.1 | 15 / 15 | |
| 0.17.0 | 15 / 15 | |
| 0.16.10 | 15 / 15 | |
| 0.16.9 | 15 / 15 | |
| 0.16.8 | 15 / 15 | |
| 0.16.7 | 15 / 15 | |
| 0.16.6 | 15 / 15 | |
| 0.16.5 | 15 / 15 | |
| 0.16.4 | 15 / 15 | |
| 0.16.1 | 15 / 15 | |
| 0.16.0 | 15 / 15 | |
| 0.15.12 | 15 / 15 | |
| 0.15.11 | 15 / 15 | |
| 0.15.7 | 15 / 15 | |
| 0.15.6 | 15 / 15 | |
| 0.15.5 | 15 / 15 | |
| 0.15.4 | 15 / 15 |
v0.48.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.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.
v0.27.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.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.
v0.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.
v0.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.
v0.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.
v0.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.
v0.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.
v0.24.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.24.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.23.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.23.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.23.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.22.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.
v0.22.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.22.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.22.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.21.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.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.