@robotical/jumping-game
1) make changes to the code 2) build using npm run build:dev 3) make sure you've linked jumping-game to webapp with npm link ../jumping-game 3.1) but also make sure you keep the other links in webapp npm link ../jumping-game ../robotical.raftjs ../rob
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is declared as a runtime dep; phantom-dep heuristic fires but it may be used indirectly via config/runtime paths. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.21 | 5 / 16 | |
| 0.1.20 | 5 / 14 | |
| 0.1.19 | 5 / 14 | |
| 0.1.18 | 5 / 14 | |
| 0.1.17 | 5 / 14 | |
| 0.1.16 | 5 / 14 | |
| 0.1.15 | 4 / 13 |
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.