@enso-ui/themes
Theme registration and Bulma style bundle for Enso 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 — 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vuex | AI (phantom-deps): Themes package declares vuex as a peer/runtime dep referenced in config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:bulma-extensions | AI (phantom-deps): Same as bulma — CSS/config reference pattern, not a real phantom dep issue. | ai | |
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): Theme package references bulma in SCSS/config, not JS imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer/config dependency for this UI theme package; not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@enso-ui/ui | AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/localisation | AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Declared runtime dependency; referenced in theme config as expected. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Declared runtime dependency; referenced in theme config as expected. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Declared runtime dependency; referenced in theme config as expected. | ai | |
| phantom-deps | phantom-dep:flatpickr | AI (phantom-deps): Declared runtime dependency; referenced in theme config as expected. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.3.47 | 4 / 5 | |
| 3.3.46 | 4 / 5 | |
| 3.3.43 | 4 / 5 | |
| 3.3.42 | 4 / 5 | |
| 3.3.41 | 4 / 5 | |
| 3.3.37 | 4 / 5 | |
| 3.3.35 | 4 / 5 | |
| 3.3.34 | 4 / 5 | |
| 3.3.33 | 4 / 5 | |
| 3.3.32 | 4 / 5 | |
| 3.3.31 | 4 / 5 | |
| 3.3.30 | 4 / 5 | |
| 3.3.29 | 4 / 5 | |
| 3.3.28 | 4 / 5 | |
| 3.3.27 | 4 / 5 | |
| 3.3.26 | 4 / 5 | |
| 3.3.25 | 4 / 5 | |
| 3.3.23 | 4 / 5 | |
| 3.3.22 | 4 / 5 | |
| 3.3.21 | 4 / 5 | |
| 3.3.20 | 4 / 5 | |
| 3.3.19 | 4 / 5 | |
| 3.3.18 | 4 / 5 | |
| 3.3.17 | 4 / 5 | |
| 3.3.16 | 4 / 5 | |
| 3.3.15 | 4 / 5 | |
| 3.3.14 | 4 / 5 | |
| 3.3.13 | 4 / 5 | |
| 3.3.12 | 6 / 3 | |
| 3.3.11 | 6 / 3 | |
| 3.3.10 | 9 / 0 | |
| 3.3.9 | 9 / 0 | |
| 3.3.7 | 9 / 0 | |
| 3.3.3 | 9 / 0 | |
| 3.3.0 | 10 / 0 | |
| 3.2.0 | 10 / 0 | |
| 3.1.0 | 7 / 9 |
v3.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.