@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 — 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: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 58 of 58)
| 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 |
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.277
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.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.275
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.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.272
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.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.270
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.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.268
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.267
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.266
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.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.