@multi-game-engines/adapter-gnubg
GNU Backgammon adapter for multi-game-engines ecosystem
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@multi-game-engines/registry | AI (dependencies): Sibling package in the same monorepo/ecosystem; risk tracks the parent org, not this dep independently. | ai | |
| dependencies | unvetted-dep:@multi-game-engines/i18n-common | AI (dependencies): Sibling package in the same monorepo/ecosystem; same rationale as registry dep. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 2 / 6 | |
| 0.1.6 | 2 / 6 | |
| 0.1.5 | 2 / 6 | |
| 0.1.4 | 2 / 6 | |
| 0.1.2 | 2 / 6 | |
| 0.1.1 | 2 / 6 | |
| 0.1.0 | 2 / 6 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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.