← Home

@blocklet/ai-runtime

100
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

wangshijungxw

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@arcblock/did-connect AI (dependencies): Same Arcblock org as this package; stable dependency across many versions. ai
provenance no-provenance AI (provenance): Established org package; lack of Sigstore provenance is consistent across all versions and poses no elevated risk here. ai
dependencies unvetted-dep:@blocklet/dataset-sdk AI (dependencies): Same @blocklet org scope; consistent with package's established ecosystem. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher has 198 approved packages and 0 rejections; org-level release cadence explains gaps. ai
phantom-deps phantom-dep:semver AI (phantom-deps): Large multi-export package; phantom-dep heuristic unreliable for bundled/config-referenced deps. ai
phantom-deps phantom-dep:express AI (phantom-deps): Express is a peer/optional server dep referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:node-fetch AI (phantom-deps): Isomorphic fetch dep referenced in config; stable false positive. ai
phantom-deps phantom-dep:json-logic-js AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@types/express AI (phantom-deps): Type-only dep; framework-scoped, stable false positive. ai
phantom-deps phantom-dep:@blocklet/co-git AI (phantom-deps): Same-org dep; stable false positive for this package. ai
phantom-deps phantom-dep:@types/file-saver AI (phantom-deps): Type-only dep; stable false positive. ai
phantom-deps phantom-dep:@blocklet/constant AI (phantom-deps): Same-org dep; stable false positive. ai
phantom-deps phantom-dep:react-querybuilder AI (phantom-deps): Declared runtime dep; stable false positive. ai
phantom-deps phantom-dep:@types/react-scroll-to-bottom AI (phantom-deps): Type-only dep; stable false positive. ai
phantom-deps phantom-dep:@types/react-syntax-highlighter AI (phantom-deps): Type-only dep; stable false positive. ai

Versions (showing 100 of 262)

Version Deps Published
0.7.13 63 / 18
0.7.12 63 / 18
0.7.11 63 / 18
0.7.8 63 / 18
0.7.7 63 / 18
0.7.6 63 / 18
0.7.5 63 / 18
0.7.4 63 / 18
0.7.3 63 / 18
0.7.2 63 / 18
0.7.1 63 / 18
0.7.0 63 / 18
0.6.3 63 / 18
0.6.2 63 / 18
0.6.1 63 / 18
0.6.0 63 / 18
0.5.26 63 / 18
0.5.25 63 / 18
0.5.24 63 / 18
0.5.23 63 / 18
0.5.22 63 / 18
0.5.21 63 / 18
0.5.20 63 / 18
0.5.19 63 / 18
0.5.18 63 / 18
0.5.17 63 / 18
0.5.16 63 / 18
0.5.15 63 / 18
0.5.14 63 / 18
0.5.13 63 / 18
0.5.12 63 / 18
0.5.11 63 / 18
0.5.10 63 / 18
0.5.9 63 / 18
0.5.8 63 / 18
0.5.7 63 / 18
0.5.6 63 / 18
0.5.5 63 / 18
0.5.4 63 / 18
0.5.3 63 / 18
0.5.2 63 / 18
0.5.1 63 / 18
0.5.0 63 / 18
0.4.279 62 / 18
0.4.278 62 / 18
0.4.277 62 / 18
0.4.276 62 / 18
0.4.275 63 / 18
0.4.274 63 / 18
0.4.273 63 / 18
0.4.272 63 / 18
0.4.271 63 / 18
0.4.270 63 / 18
0.4.269 63 / 18
0.4.268 63 / 18
0.4.267 63 / 18
0.4.266 63 / 18
0.4.265 63 / 18
0.4.264 63 / 18
0.4.263 63 / 18
0.4.262 63 / 18
0.4.261 63 / 18
0.4.260 63 / 18
0.4.259 63 / 18
0.4.258 63 / 18
0.4.257 63 / 18
0.4.256 63 / 18
0.4.255 63 / 18
0.4.254 63 / 18
0.4.253 63 / 18
0.4.252 63 / 18
0.4.251 63 / 18
0.4.250 63 / 18
0.4.249 63 / 18
0.4.248 63 / 18
0.4.247 63 / 18
0.4.246 63 / 18
0.4.245 63 / 18
0.4.244 63 / 18
0.4.243 63 / 18
0.4.242 63 / 18
0.4.241 63 / 18
0.4.240 63 / 18
0.4.239 63 / 18
0.4.238 63 / 18
0.4.237 63 / 18
0.4.236 63 / 18
0.4.235 63 / 18
0.4.234 63 / 18
0.4.233 62 / 18
0.4.232 62 / 18
0.4.231 62 / 18
0.4.230 62 / 18
0.4.229 62 / 18
0.4.228 62 / 18
0.4.227 62 / 18
0.4.226 62 / 18
0.4.225 62 / 18
0.4.224 62 / 18
0.4.223 62 / 18
Showing 100 of 262 Next page →

v0.4.264

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.