@robotical/skiing-game
1) make changes to the code 2) build using npm run build:dev 3) make sure you've linked skiing-game to webapp with npm link ../skiing-game 3.1) but also make sure you keep the other links in webapp npm link ../skiing-game ../robotical.raftjs ../roboti
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:tests/e2e/visual-phases.e2e.js | AI (source-diff): Puppeteer e2e visual test using localhost server + child_process spawn; standard test pattern. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a declared runtime dependency; phantom-dep false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private org game component; sparse public metadata is expected for internal @robotical packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.24 | 6 / 15 | |
| 0.1.23 | 6 / 15 | |
| 0.1.22 | 6 / 15 | |
| 0.1.21 | 6 / 14 | |
| 0.1.19 | 6 / 14 | |
| 0.1.18 | 6 / 14 | |
| 0.1.17 | 6 / 14 | |
| 0.1.16 | 6 / 14 | |
| 0.1.15 | 6 / 14 |
v0.1.24
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.