@phila/phila-ui-core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/BaseLink.vue_vue_type_script_setup_true_lang-DYewXFgw.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component bundle; code is readable Vue logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/BaseLink.vue_vue_type_script_setup_true_lang-CexJ6lNf.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for a Vue component library; not obfuscation. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 1 / 9 | |
| 2.3.2 | 1 / 9 | |
| 2.3.1 | 1 / 9 | |
| 2.3.0 | 1 / 9 | |
| 2.2.0 | 1 / 9 | |
| 2.1.2 | 1 / 9 | |
| 2.1.1 | 1 / 9 | |
| 2.1.0 | 1 / 9 | |
| 2.0.1 | 1 / 9 | |
| 2.0.0 | 1 / 9 |
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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.2.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.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.