koishi
4
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
shigma
Keywords
botchatbotdiscordtelegramcordisframework
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Koishi is a CLI chatbot framework; child_process is used to spawn worker processes — a documented and expected pattern for this package across all versions. | ai | |
| phantom-deps | phantom-dep:@satorijs/core | AI (phantom-deps): Koishi uses a plugin architecture; @satorijs/core is a declared runtime dep loaded dynamically, not via static import. Expected pattern for this framework. | ai | |
| phantom-deps | phantom-dep:@koishijs/plugin-http | AI (phantom-deps): Plugin dependency loaded dynamically via Koishi's plugin system, not via static import. Expected pattern for this framework. | ai | |
| phantom-deps | phantom-dep:@koishijs/plugin-server | AI (phantom-deps): Plugin dependency loaded dynamically via Koishi's plugin system, not via static import. Expected pattern for this framework. | ai | |
| phantom-deps | phantom-dep:@koishijs/plugin-proxy-agent | AI (phantom-deps): Plugin dependency loaded dynamically via Koishi's plugin system, not via static import. Expected pattern for this framework. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.18.11 | 9 / 0 | |
| 4.18.10 | 9 / 0 | |
| 4.18.9 | 9 / 0 | |
| 4.18.8 | 9 / 0 |
v4.18.11
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.18.9
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.8
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.