← Home

@robotical/jumping-game

npm Repository Homepage

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

17
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
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 17 of 17)

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
0.1.14 4 / 13
0.1.13 5 / 13
0.1.11 5 / 13
0.1.10 5 / 13
0.1.9 5 / 13
0.1.8 4 / 13
0.1.7 4 / 13
0.1.6 4 / 13
0.1.5 3 / 14
0.1.3 3 / 15

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.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.10

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

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.3

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.