@multi-game-engines/ui-shogi-elements
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely a CI/publish environment change; no other risk signals present and package content is unchanged from prior version. | ai | |
| dependencies | unvetted-dep:@multi-game-engines/core | AI (dependencies): Same-monorepo sibling dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@multi-game-engines/domain-shogi | AI (dependencies): Same-monorepo sibling dependency; expected for this package family. | ai |
v0.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maigmz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.