@world-forge/editor
Web-based world authoring editor
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:@world-forge/renderer-2d | AI (phantom-deps): Same-org sibling dep; likely used transitively or via re-export rather than direct import. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 7 / 4 | |
| 4.0.2 | 6 / 4 | |
| 3.9.0 | 6 / 4 | |
| 3.1.0 | 6 / 4 | |
| 2.4.0 | 6 / 4 | |
| 2.3.0 | 6 / 4 | |
| 2.0.0 | 6 / 4 | |
| 1.9.1 | 6 / 4 | |
| 1.8.1 | 6 / 4 |
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.