@hieuzest/koishi-plugin-mahjongpub
Mahjong.pub API
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small niche plugin; no CI/CD provenance is consistent across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established plugin with 55 versions and 1.9k weekly downloads; sparse README/no repo URL is typical for niche Koishi ecosystem plugins. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.13 | 2 / 12 | |
| 0.3.9 | 2 / 12 | |
| 0.3.1 | 2 / 12 | |
| 0.3.0 | 2 / 12 | |
| 0.2.17 | 2 / 9 | |
| 0.2.14 | 2 / 9 | |
| 0.2.7 | 1 / 0 |
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.