@opentui/solid
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:s-js | AI (dependencies): s-js is the reactive core of solid-js; legitimate dependency for a SolidJS renderer package. | ai | |
| phantom-deps | phantom-dep:s-js | AI (phantom-deps): s-js is SolidJS reactive core; used transitively via babel-preset-solid, not directly imported. | ai | |
| phantom-deps | phantom-dep:babel-plugin-module-resolver | AI (phantom-deps): Build-time babel plugin referenced in config, not directly imported in source — stable false positive. | ai |
Versions (showing 51 of 122)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 7 / 6 | |
| 0.3.1 | 7 / 6 | |
| 0.3.0 | 7 / 6 | |
| 0.2.16 | 7 / 6 | |
| 0.2.15 | 7 / 6 | |
| 0.2.14 | 7 / 6 | |
| 0.2.13 | 7 / 6 | |
| 0.2.12 | 7 / 6 | |
| 0.2.11 | 7 / 6 | |
| 0.2.10 | 7 / 6 | |
| 0.2.9 | 7 / 6 | |
| 0.2.8 | 7 / 6 | |
| 0.2.7 | 7 / 6 | |
| 0.2.6 | 7 / 6 | |
| 0.2.5 | 7 / 6 | |
| 0.2.4 | 7 / 6 | |
| 0.2.3 | 7 / 6 | |
| 0.2.2 | 7 / 6 | |
| 0.2.1 | 7 / 6 | |
| 0.2.0 | 7 / 6 | |
| 0.1.107 | 7 / 6 | |
| 0.1.106 | 7 / 6 | |
| 0.1.105 | 7 / 5 | |
| 0.1.104 | 7 / 5 | |
| 0.1.103 | 7 / 5 | |
| 0.1.102 | 7 / 5 | |
| 0.1.101 | 7 / 5 | |
| 0.1.100 | 7 / 5 | |
| 0.1.99 | 7 / 5 | |
| 0.1.98 | 7 / 5 | |
| 0.1.97 | 7 / 5 | |
| 0.1.96 | 7 / 5 | |
| 0.1.95 | 7 / 5 | |
| 0.1.94 | 7 / 5 | |
| 0.1.93 | 7 / 5 | |
| 0.1.92 | 7 / 5 | |
| 0.1.91 | 7 / 5 | |
| 0.1.90 | 7 / 5 | |
| 0.1.89 | 7 / 5 | |
| 0.1.88 | 7 / 5 | |
| 0.1.87 | 7 / 4 | |
| 0.1.86 | 6 / 4 | |
| 0.1.85 | 6 / 4 | |
| 0.1.84 | 6 / 4 | |
| 0.1.83 | 6 / 4 | |
| 0.1.82 | 6 / 4 | |
| 0.1.81 | 6 / 4 | |
| 0.1.80 | 6 / 4 | |
| 0.1.79 | 6 / 4 | |
| 0.1.78 | 6 / 4 | |
| 0.1.77 | 6 / 4 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.