@koishijs/market
Market UI for Koishi
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@koishijs/components | AI (dependencies): Same-org dependency (@koishijs scope); expected intra-organization dependency for this UI package. Not a meaningful risk signal. | ai | |
| license | copyleft-license:AGPL-3.0 | AI (license): AGPL-3.0 is intentionally declared by the author; this is a known open-source Koishi ecosystem package. License is stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 33 versions and 1474 days of history; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:spark-md5 | AI (phantom-deps): spark-md5 is a declared runtime dependency used in the client bundle; phantom detection is a false positive for this build-tool-oriented package. | ai | |
| phantom-deps | phantom-dep:@koishijs/components | AI (phantom-deps): Same-org dependency used indirectly through the Koishi client framework; phantom detection is a false positive here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.2.10 | 3 / 2 | |
| 4.2.9 | 3 / 2 | |
| 4.2.8 | 3 / 2 | |
| 4.2.7 | 3 / 2 | |
| 4.2.6 | 3 / 2 | |
| 4.2.5 | 3 / 2 | |
| 4.2.4 | 3 / 2 | |
| 4.2.3 | 3 / 2 | |
| 4.2.2 | 3 / 2 | |
| 4.2.1 | 3 / 2 | |
| 4.2.0 | 3 / 2 | |
| 4.1.8 | 3 / 2 | |
| 4.1.7 | 3 / 2 | |
| 4.1.6 | 3 / 2 | |
| 4.1.5 | 3 / 2 | |
| 4.1.4 | 3 / 2 | |
| 4.1.3 | 3 / 2 | |
| 4.1.2 | 3 / 2 | |
| 4.1.1 | 3 / 2 | |
| 4.1.0 | 3 / 2 | |
| 4.0.1 | 3 / 2 | |
| 4.0.0 | 3 / 2 |
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.