@blocklet/aigne-hub
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:recoil | AI (dependencies): Phantom dep flagged as accepted risk; not directly imported, listed for peer-dep compatibility. | ai | |
| dependencies | unvetted-dep:sequelize | AI (dependencies): Phantom dep flagged as accepted risk; not directly imported, listed for peer-dep compatibility. | ai | |
| phantom-deps | phantom-dep:recoil | AI (phantom-deps): Component library; recoil declared as dep but used via config/peer pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:sequelize | AI (phantom-deps): Declared dep used in config scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:joi | AI (phantom-deps): Declared dep used in config scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Declared dep used in config scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Declared dep used in config scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Declared dep used in config scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Framework-scoped type package; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.9.15 | 37 / 18 | |
| 0.9.14 | 37 / 18 | |
| 0.9.13 | 37 / 18 | |
| 0.9.12 | 37 / 18 | |
| 0.9.0 | 37 / 18 | |
| 0.8.5 | 37 / 18 | |
| 0.8.4 | 37 / 18 | |
| 0.8.3 | 37 / 18 | |
| 0.7.20 | 37 / 18 | |
| 0.6.27 | 37 / 18 | |
| 0.6.25 | 37 / 18 | |
| 0.6.16 | 37 / 18 | |
| 0.6.14 | 37 / 18 | |
| 0.6.8 | 37 / 18 | |
| 0.6.7 | 37 / 18 | |
| 0.6.5 | 37 / 18 | |
| 0.6.4 | 37 / 18 | |
| 0.2.7 | 35 / 18 |
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.