@blocklet/ai-kit
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:sequelize | AI (dependencies): sequelize is a well-known ORM; phantom-dep finding confirms it's not directly imported, reducing actual risk. | ai | |
| phantom-deps | phantom-dep:recoil | AI (phantom-deps): State management dep declared but may be re-exported; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Utility hooks dep declared; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:joi | AI (phantom-deps): Declared for config validation; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Emotion peer/dep declared for MUI; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only dep; expected not to be directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:sequelize | AI (phantom-deps): ORM dep declared for server-side use; stable false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 35 / 18 | |
| 0.2.5 | 35 / 18 | |
| 0.2.4 | 33 / 18 | |
| 0.2.0 | 33 / 18 | |
| 0.1.78 | 33 / 20 | |
| 0.1.77 | 33 / 20 | |
| 0.1.76 | 33 / 20 |
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.