@lvce-editor/server
Run LVCE Editor as a server.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @lvce-editor/server package; 1400+ day old project with 762 versions — not a typosquat of semver. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Server launcher spreading process.env to worker processes is expected and documented behavior for this package. | ai | |
| phantom-deps | phantom-dep:@lvce-editor/static-server | AI (phantom-deps): Same-org scoped dep; may be loaded dynamically or transitively — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lvce-editor/shared-process | AI (phantom-deps): Same-org scoped dep; may be loaded dynamically or transitively — stable false positive for this package. | ai |
Versions (showing 100 of 526)
| Version | Deps | Published |
|---|---|---|
| 0.52.9 | 2 / 0 | |
| 0.52.8 | 2 / 0 | |
| 0.52.7 | 2 / 0 | |
| 0.52.6 | 2 / 0 | |
| 0.52.5 | 2 / 0 | |
| 0.52.4 | 2 / 0 | |
| 0.52.3 | 2 / 0 | |
| 0.52.2 | 2 / 0 | |
| 0.52.1 | 2 / 0 | |
| 0.52.0 | 2 / 0 | |
| 0.51.4 | 2 / 0 | |
| 0.51.3 | 2 / 0 | |
| 0.51.2 | 2 / 0 | |
| 0.51.1 | 2 / 0 | |
| 0.51.0 | 2 / 0 | |
| 0.50.2 | 2 / 0 | |
| 0.50.1 | 2 / 0 | |
| 0.50.0 | 2 / 0 | |
| 0.49.24 | 2 / 0 | |
| 0.49.23 | 2 / 0 | |
| 0.49.22 | 2 / 0 | |
| 0.49.21 | 2 / 0 | |
| 0.49.20 | 2 / 0 | |
| 0.49.19 | 2 / 0 | |
| 0.49.18 | 2 / 0 | |
| 0.49.17 | 2 / 0 | |
| 0.49.16 | 2 / 0 | |
| 0.49.15 | 2 / 0 | |
| 0.49.14 | 2 / 0 | |
| 0.49.13 | 2 / 0 | |
| 0.49.12 | 2 / 0 | |
| 0.49.11 | 2 / 0 | |
| 0.49.10 | 2 / 0 | |
| 0.49.9 | 2 / 0 | |
| 0.49.8 | 2 / 0 | |
| 0.49.7 | 2 / 0 | |
| 0.49.6 | 2 / 0 | |
| 0.49.5 | 2 / 0 | |
| 0.49.4 | 2 / 0 | |
| 0.49.3 | 2 / 0 | |
| 0.49.2 | 2 / 0 | |
| 0.49.1 | 2 / 0 | |
| 0.49.0 | 2 / 0 | |
| 0.48.3 | 2 / 0 | |
| 0.48.2 | 2 / 0 | |
| 0.48.1 | 2 / 0 | |
| 0.48.0 | 2 / 0 | |
| 0.47.3 | 2 / 0 | |
| 0.47.2 | 2 / 0 | |
| 0.47.1 | 2 / 0 | |
| 0.47.0 | 2 / 0 | |
| 0.46.6 | 2 / 0 | |
| 0.46.5 | 2 / 0 | |
| 0.46.4 | 2 / 0 | |
| 0.46.3 | 2 / 0 | |
| 0.46.2 | 2 / 0 | |
| 0.46.1 | 2 / 0 | |
| 0.46.0 | 2 / 0 | |
| 0.45.26 | 2 / 0 | |
| 0.45.25 | 2 / 0 | |
| 0.45.24 | 2 / 0 | |
| 0.45.23 | 2 / 0 | |
| 0.45.22 | 2 / 0 | |
| 0.45.21 | 2 / 0 | |
| 0.45.20 | 2 / 0 | |
| 0.45.19 | 2 / 0 | |
| 0.45.18 | 2 / 0 | |
| 0.45.17 | 2 / 0 | |
| 0.45.16 | 2 / 0 | |
| 0.45.15 | 2 / 0 | |
| 0.45.14 | 2 / 0 | |
| 0.45.13 | 2 / 0 | |
| 0.45.12 | 2 / 0 | |
| 0.45.11 | 2 / 0 | |
| 0.45.10 | 2 / 0 | |
| 0.45.9 | 2 / 0 | |
| 0.45.8 | 2 / 0 | |
| 0.45.7 | 2 / 0 | |
| 0.45.6 | 2 / 0 | |
| 0.45.5 | 2 / 0 | |
| 0.45.4 | 2 / 0 | |
| 0.45.3 | 2 / 0 | |
| 0.45.2 | 2 / 0 | |
| 0.45.1 | 2 / 0 | |
| 0.45.0 | 2 / 0 | |
| 0.44.8 | 2 / 0 | |
| 0.44.7 | 2 / 0 | |
| 0.44.6 | 2 / 0 | |
| 0.44.5 | 2 / 0 | |
| 0.44.4 | 2 / 0 | |
| 0.44.3 | 2 / 0 | |
| 0.44.2 | 2 / 0 | |
| 0.44.1 | 2 / 0 | |
| 0.44.0 | 2 / 0 | |
| 0.43.5 | 2 / 0 | |
| 0.43.4 | 2 / 0 | |
| 0.43.3 | 2 / 0 | |
| 0.43.2 | 2 / 0 | |
| 0.43.1 | 2 / 0 | |
| 0.43.0 | 2 / 0 |
v0.50.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.