@fairyhunter13/opentui-solid
SolidJS renderer for OpenTUI
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:s-js | AI (phantom-deps): s-js is explicitly declared as a runtime dependency; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@fairyhunter13/opentui-core | AI (phantom-deps): Same-org sibling dep; declared in dependencies and used as a peer/runtime dep by the renderer. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.1.142 | 7 / 6 | |
| 0.1.141 | 7 / 5 | |
| 0.1.140 | 7 / 5 | |
| 0.1.139 | 7 / 5 | |
| 0.1.138 | 7 / 5 | |
| 0.1.137 | 7 / 5 | |
| 0.1.136 | 7 / 5 | |
| 0.1.133 | 7 / 5 | |
| 0.1.132 | 7 / 5 | |
| 0.1.130 | 7 / 5 | |
| 0.1.129 | 7 / 5 | |
| 0.1.128 | 7 / 5 | |
| 0.1.127 | 7 / 5 | |
| 0.1.126 | 7 / 5 | |
| 0.1.125 | 7 / 5 | |
| 0.1.124 | 7 / 5 | |
| 0.1.121 | 7 / 5 | |
| 0.1.120 | 7 / 5 | |
| 0.1.119 | 7 / 5 | |
| 0.1.118 | 7 / 5 | |
| 0.1.117 | 7 / 5 | |
| 0.1.116 | 7 / 5 | |
| 0.1.114 | 7 / 5 | |
| 0.1.113 | 7 / 5 | |
| 0.1.112 | 7 / 5 | |
| 0.1.111 | 7 / 5 | |
| 0.1.110 | 7 / 5 | |
| 0.1.109 | 7 / 5 | |
| 0.1.108 | 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.94 | 7 / 5 | |
| 0.1.93 | 7 / 5 | |
| 0.1.92 | 7 / 5 | |
| 0.1.91 | 7 / 5 | |
| 0.1.89 | 7 / 5 | |
| 0.1.88 | 7 / 5 |
v0.1.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.112
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fairyhunter13.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.108
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.