@koishijs/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@minatojs/core | AI (dependencies): Sibling package from same Koishi monorepo ecosystem. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Monorepo refactor splitting core into sibling packages, not third-party additions. | ai | |
| source-diff | obfuscated-file-transition:lib/browser.js | AI (source-diff): Browser bundle entry point; minified build output, not obfuscated payload. | ai | |
| dependencies | unvetted-dep:@koishijs/orm | AI (dependencies): First-party koishijs org package, same monorepo as core. | ai | |
| dependencies | unvetted-dep:cordis | AI (dependencies): cordis is the DI framework by the same author (Shigma) and is a foundational dependency of the Koishi ecosystem; not a suspicious or unvetted dependency. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @koishijs/core is the core package of the Koishi chatbot framework, not a typosquat of 'cors'. The name similarity is coincidental (core vs cors); scoped package with 171 versions and SLSA provenance. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.18.11 | 7 / 6 | |
| 4.18.10 | 7 / 6 | |
| 4.18.8 | 7 / 6 | |
| 4.16.4 | 7 / 3 | |
| 4.15.7 | 7 / 3 | |
| 4.7.0 | 4 / 5 | |
| 4.5.0 | 3 / 5 | |
| 4.4.2 | 2 / 5 | |
| 4.4.1 | 3 / 5 | |
| 4.4.0 | 3 / 5 | |
| 4.3.3 | 3 / 5 | |
| 4.3.2 | 3 / 5 | |
| 4.3.1 | 3 / 5 | |
| 4.3.0 | 3 / 5 | |
| 4.2.2 | 3 / 5 | |
| 4.2.1 | 3 / 5 | |
| 4.2.0 | 3 / 5 | |
| 4.1.2 | 3 / 5 | |
| 4.1.1 | 3 / 5 | |
| 4.1.0 | 3 / 5 | |
| 4.0.1 | 3 / 5 | |
| 4.0.0 | 3 / 5 |
v4.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.