← Home

@robotical/skiing-game

npm

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

16
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

robdobsnrobotical-sandynikthegeek

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 16 of 16)

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
0.1.14 5 / 13
0.1.13 5 / 13
0.1.12 5 / 13
0.1.11 5 / 13
0.1.9 5 / 13
0.1.8 4 / 13
0.1.7 4 / 13

v0.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.