@robotical/maze
1) make changes to the code 2) build using npm run build:dev 3) make sure you've linked maze to webapp with npm link ../maze 3.1) but also make sure you keep the other links in webapp npm link ../maze ../robotical.raftjs ../roboticaljs 3.2) if you
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 used at runtime via require in non-entry files; phantom-dep heuristic miss. | ai | |
| phantom-deps | phantom-dep:generate-maze | AI (phantom-deps): generate-maze is used at runtime; phantom-dep heuristic miss on compiled output. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.1.17 | 5 / 14 | |
| 0.1.16 | 5 / 14 | |
| 0.1.15 | 5 / 13 | |
| 0.1.14 | 5 / 13 |
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. 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.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.