@blocklet/aigne-sdk
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): Declared as runtime dep, likely re-exported or used indirectly; stable false positive for this SDK package. | ai | |
| provenance | no-provenance | AI (provenance): Arcblock org packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Same pattern — declared dep used indirectly or re-exported; stable false positive. | ai | |
| phantom-deps | phantom-dep:ahooks | AI (phantom-deps): React hook library likely used in component exports; stable false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Utility dep used indirectly; stable false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Form library used in component exports; stable false positive. | ai | |
| phantom-deps | phantom-dep:eventsource-parser | AI (phantom-deps): SSE parsing dep used indirectly; stable false positive for this SDK. | ai | |
| phantom-deps | phantom-dep:joi | AI (phantom-deps): SDK package re-exports or uses deps indirectly; phantom-dep false positive for this package. | ai |
Versions (showing 100 of 339)
| Version | Deps | Published |
|---|---|---|
| 0.7.13 | 14 / 16 | |
| 0.7.12 | 14 / 16 | |
| 0.7.11 | 14 / 16 | |
| 0.7.8 | 14 / 16 | |
| 0.7.7 | 14 / 16 | |
| 0.7.6 | 14 / 16 | |
| 0.7.5 | 14 / 16 | |
| 0.7.4 | 14 / 16 | |
| 0.7.3 | 14 / 16 | |
| 0.7.2 | 14 / 16 | |
| 0.7.1 | 14 / 16 | |
| 0.7.0 | 14 / 16 | |
| 0.6.3 | 14 / 16 | |
| 0.6.2 | 14 / 16 | |
| 0.6.1 | 14 / 16 | |
| 0.6.0 | 14 / 16 | |
| 0.5.26 | 14 / 16 | |
| 0.5.25 | 14 / 16 | |
| 0.5.24 | 14 / 16 | |
| 0.5.23 | 14 / 16 | |
| 0.5.22 | 14 / 16 | |
| 0.5.21 | 14 / 16 | |
| 0.5.20 | 14 / 16 | |
| 0.5.19 | 14 / 16 | |
| 0.5.18 | 14 / 16 | |
| 0.5.17 | 14 / 16 | |
| 0.5.16 | 14 / 16 | |
| 0.5.15 | 14 / 16 | |
| 0.5.14 | 14 / 16 | |
| 0.5.13 | 14 / 16 | |
| 0.5.12 | 14 / 16 | |
| 0.5.11 | 14 / 16 | |
| 0.5.10 | 14 / 16 | |
| 0.5.9 | 14 / 16 | |
| 0.5.8 | 14 / 16 | |
| 0.5.7 | 14 / 16 | |
| 0.5.6 | 14 / 16 | |
| 0.5.5 | 14 / 16 | |
| 0.5.4 | 14 / 16 | |
| 0.5.3 | 14 / 16 | |
| 0.5.2 | 15 / 16 | |
| 0.5.1 | 15 / 16 | |
| 0.5.0 | 15 / 16 | |
| 0.4.279 | 15 / 16 | |
| 0.4.278 | 15 / 16 | |
| 0.4.277 | 15 / 16 | |
| 0.4.276 | 15 / 16 | |
| 0.4.275 | 15 / 16 | |
| 0.4.274 | 15 / 16 | |
| 0.4.273 | 15 / 16 | |
| 0.4.272 | 15 / 16 | |
| 0.4.271 | 15 / 16 | |
| 0.4.270 | 15 / 16 | |
| 0.4.269 | 15 / 16 | |
| 0.4.268 | 15 / 16 | |
| 0.4.267 | 15 / 16 | |
| 0.4.266 | 15 / 16 | |
| 0.4.265 | 15 / 16 | |
| 0.4.264 | 15 / 16 | |
| 0.4.263 | 15 / 16 | |
| 0.4.262 | 15 / 16 | |
| 0.4.261 | 15 / 16 | |
| 0.4.260 | 15 / 16 | |
| 0.4.259 | 15 / 16 | |
| 0.4.258 | 15 / 16 | |
| 0.4.257 | 15 / 16 | |
| 0.4.256 | 15 / 16 | |
| 0.4.255 | 15 / 16 | |
| 0.4.254 | 15 / 16 | |
| 0.4.253 | 15 / 16 | |
| 0.4.252 | 15 / 16 | |
| 0.4.251 | 15 / 16 | |
| 0.4.250 | 15 / 16 | |
| 0.4.249 | 15 / 16 | |
| 0.4.248 | 15 / 16 | |
| 0.4.247 | 15 / 16 | |
| 0.4.246 | 15 / 16 | |
| 0.4.245 | 15 / 16 | |
| 0.4.244 | 15 / 16 | |
| 0.4.243 | 15 / 16 | |
| 0.4.242 | 15 / 16 | |
| 0.4.241 | 15 / 16 | |
| 0.4.240 | 15 / 16 | |
| 0.4.239 | 15 / 16 | |
| 0.4.238 | 15 / 16 | |
| 0.4.237 | 15 / 16 | |
| 0.4.236 | 15 / 16 | |
| 0.4.235 | 15 / 16 | |
| 0.4.234 | 15 / 16 | |
| 0.4.233 | 15 / 16 | |
| 0.4.232 | 15 / 16 | |
| 0.4.231 | 15 / 16 | |
| 0.4.230 | 15 / 16 | |
| 0.4.229 | 15 / 16 | |
| 0.4.228 | 15 / 16 | |
| 0.4.227 | 15 / 16 | |
| 0.4.226 | 15 / 16 | |
| 0.4.225 | 15 / 16 | |
| 0.4.224 | 15 / 16 | |
| 0.4.223 | 15 / 16 |
v0.4.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.259
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.256
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.255
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.254
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.253
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.252
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.251
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.250
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.249
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.247
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.244
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.241
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.240
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.238
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.237
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.236
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.235
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.234
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.233
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.232
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.231
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.230
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.229
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.228
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.227
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.226
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.225
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.224
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.223
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.