@newhighsco/press-start
Chipset + Next.js site starter by New High Score
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 100 of 407)
| Version | Deps | Published |
|---|---|---|
| 2.3.251 | 1 / 13 | |
| 2.3.250 | 1 / 13 | |
| 2.3.249 | 1 / 13 | |
| 2.3.248 | 1 / 13 | |
| 2.3.247 | 1 / 13 | |
| 2.3.246 | 1 / 13 | |
| 2.3.245 | 1 / 13 | |
| 2.3.244 | 1 / 13 | |
| 2.3.243 | 1 / 13 | |
| 2.3.242 | 1 / 13 | |
| 2.3.241 | 1 / 13 | |
| 2.3.240 | 1 / 13 | |
| 2.3.239 | 1 / 13 | |
| 2.3.238 | 1 / 13 | |
| 2.3.237 | 1 / 13 | |
| 2.3.236 | 1 / 13 | |
| 2.3.235 | 1 / 13 | |
| 2.3.234 | 1 / 13 | |
| 2.3.233 | 1 / 13 | |
| 2.3.232 | 1 / 13 | |
| 2.3.231 | 1 / 13 | |
| 2.3.230 | 1 / 13 | |
| 2.3.229 | 1 / 13 | |
| 2.3.228 | 1 / 13 | |
| 2.3.227 | 1 / 13 | |
| 2.3.226 | 1 / 13 | |
| 2.3.225 | 1 / 13 | |
| 2.3.224 | 1 / 13 | |
| 2.3.223 | 1 / 13 | |
| 2.3.222 | 1 / 13 | |
| 2.3.221 | 1 / 13 | |
| 2.3.220 | 1 / 13 | |
| 2.3.219 | 1 / 13 | |
| 2.3.218 | 1 / 13 | |
| 2.3.217 | 1 / 13 | |
| 2.3.216 | 1 / 13 | |
| 2.3.215 | 1 / 13 | |
| 2.3.214 | 1 / 13 | |
| 2.3.213 | 1 / 13 | |
| 2.3.212 | 1 / 13 | |
| 2.3.211 | 1 / 13 | |
| 2.3.210 | 1 / 13 | |
| 2.3.209 | 1 / 13 | |
| 2.3.208 | 1 / 13 | |
| 2.3.207 | 1 / 13 | |
| 2.3.206 | 1 / 13 | |
| 2.3.205 | 1 / 13 | |
| 2.3.204 | 1 / 13 | |
| 2.3.203 | 1 / 13 | |
| 2.3.202 | 1 / 13 | |
| 2.3.201 | 1 / 13 | |
| 2.3.200 | 1 / 13 | |
| 2.3.199 | 1 / 13 | |
| 2.3.198 | 1 / 13 | |
| 2.3.197 | 1 / 13 | |
| 2.3.196 | 1 / 13 | |
| 2.3.195 | 1 / 13 | |
| 2.3.194 | 1 / 13 | |
| 2.3.193 | 1 / 13 | |
| 2.3.192 | 1 / 13 | |
| 2.3.191 | 1 / 13 | |
| 2.3.190 | 1 / 13 | |
| 2.3.189 | 1 / 13 | |
| 2.3.188 | 1 / 13 | |
| 2.3.187 | 1 / 13 | |
| 2.3.186 | 1 / 13 | |
| 2.3.185 | 1 / 13 | |
| 2.3.184 | 1 / 13 | |
| 2.3.183 | 1 / 13 | |
| 2.3.182 | 1 / 13 | |
| 2.3.181 | 1 / 13 | |
| 2.3.180 | 1 / 13 | |
| 2.3.179 | 1 / 13 | |
| 2.3.178 | 1 / 13 | |
| 2.3.177 | 1 / 13 | |
| 2.3.176 | 1 / 13 | |
| 2.3.175 | 1 / 13 | |
| 2.3.174 | 1 / 13 | |
| 2.3.173 | 1 / 13 | |
| 2.3.172 | 1 / 13 | |
| 2.3.171 | 1 / 13 | |
| 2.3.170 | 1 / 13 | |
| 2.3.169 | 1 / 13 | |
| 2.3.168 | 1 / 13 | |
| 2.3.167 | 1 / 13 | |
| 2.3.166 | 1 / 13 | |
| 2.3.165 | 1 / 13 | |
| 2.3.164 | 1 / 13 | |
| 2.3.163 | 1 / 13 | |
| 2.3.162 | 1 / 13 | |
| 2.3.161 | 1 / 13 | |
| 2.3.160 | 1 / 13 | |
| 2.3.159 | 1 / 13 | |
| 2.3.158 | 1 / 13 | |
| 2.3.157 | 1 / 13 | |
| 2.3.156 | 1 / 13 | |
| 2.3.155 | 1 / 13 | |
| 2.3.154 | 1 / 13 | |
| 2.3.153 | 1 / 13 | |
| 2.3.152 | 1 / 13 |
v2.3.217
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.216
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.215
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.214
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.213
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.212
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.210
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.209
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.208
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.206
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.203
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.202
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.201
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.200
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.199
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.198
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.197
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.196
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.195
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.194
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.193
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.192
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.191
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.189
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.188
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.187
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.186
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.185
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.182
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.181
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.179
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.178
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.177
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.175
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.152
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.