@lvce-editor/shared-process
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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy trap to wrap process.argv — standard JS pattern, not obfuscation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established editor package with 795 versions; missing description is a stable characteristic, not a malice indicator. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from levivilet to GitHub Actions CI/CD is consistent with automating releases; SLSA attestation confirms integrity. | ai | |
| dependencies | unvetted-dep:@lvce-editor/json-rpc | AI (dependencies): First-party @lvce-editor scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@lvce-editor/jsonc-parser | AI (dependencies): First-party @lvce-editor scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@lvce-editor/rpc-registry | AI (dependencies): First-party @lvce-editor scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@lvce-editor/pretty-error | AI (dependencies): First-party @lvce-editor scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@lvce-editor/ipc | AI (dependencies): First-party @lvce-editor scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@lvce-editor/assert | AI (dependencies): First-party @lvce-editor scoped dep from the same monorepo; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@lvce-editor/auth-process | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic fires as false positive for this package. | ai |
Versions (showing 100 of 629)
| Version | Deps | Published |
|---|---|---|
| 0.52.4 | 11 / 0 | |
| 0.52.3 | 11 / 0 | |
| 0.52.2 | 11 / 0 | |
| 0.52.1 | 11 / 0 | |
| 0.52.0 | 11 / 0 | |
| 0.51.4 | 10 / 0 | |
| 0.51.3 | 10 / 0 | |
| 0.51.2 | 10 / 0 | |
| 0.51.1 | 10 / 0 | |
| 0.51.0 | 10 / 0 | |
| 0.50.2 | 10 / 0 | |
| 0.50.1 | 10 / 0 | |
| 0.50.0 | 10 / 0 | |
| 0.49.24 | 10 / 0 | |
| 0.49.23 | 10 / 0 | |
| 0.49.22 | 10 / 0 | |
| 0.49.21 | 10 / 0 | |
| 0.49.20 | 10 / 0 | |
| 0.49.19 | 10 / 0 | |
| 0.49.18 | 10 / 0 | |
| 0.49.17 | 10 / 0 | |
| 0.49.16 | 10 / 0 | |
| 0.49.15 | 10 / 0 | |
| 0.49.14 | 10 / 0 | |
| 0.49.13 | 10 / 0 | |
| 0.49.12 | 10 / 0 | |
| 0.49.11 | 10 / 0 | |
| 0.49.10 | 10 / 0 | |
| 0.49.9 | 10 / 0 | |
| 0.49.8 | 10 / 0 | |
| 0.49.7 | 10 / 0 | |
| 0.49.6 | 10 / 0 | |
| 0.49.5 | 10 / 0 | |
| 0.49.4 | 10 / 0 | |
| 0.49.3 | 10 / 0 | |
| 0.49.2 | 10 / 0 | |
| 0.49.1 | 10 / 0 | |
| 0.49.0 | 10 / 0 | |
| 0.48.3 | 10 / 0 | |
| 0.48.2 | 10 / 0 | |
| 0.48.1 | 10 / 0 | |
| 0.48.0 | 10 / 0 | |
| 0.47.3 | 10 / 0 | |
| 0.47.2 | 10 / 0 | |
| 0.47.1 | 10 / 0 | |
| 0.47.0 | 10 / 0 | |
| 0.46.6 | 10 / 0 | |
| 0.46.5 | 10 / 0 | |
| 0.46.4 | 10 / 0 | |
| 0.46.3 | 10 / 0 | |
| 0.46.2 | 10 / 0 | |
| 0.46.1 | 10 / 0 | |
| 0.46.0 | 10 / 0 | |
| 0.45.26 | 10 / 0 | |
| 0.45.25 | 10 / 0 | |
| 0.45.24 | 10 / 0 | |
| 0.45.23 | 10 / 0 | |
| 0.45.22 | 10 / 0 | |
| 0.45.21 | 10 / 0 | |
| 0.45.20 | 10 / 0 | |
| 0.45.19 | 10 / 0 | |
| 0.45.18 | 10 / 0 | |
| 0.45.17 | 10 / 0 | |
| 0.45.16 | 10 / 0 | |
| 0.45.15 | 10 / 0 | |
| 0.45.14 | 10 / 0 | |
| 0.45.13 | 10 / 0 | |
| 0.45.12 | 10 / 0 | |
| 0.45.11 | 10 / 0 | |
| 0.45.10 | 10 / 0 | |
| 0.45.9 | 10 / 0 | |
| 0.45.8 | 10 / 0 | |
| 0.45.7 | 10 / 0 | |
| 0.45.6 | 10 / 0 | |
| 0.45.5 | 10 / 0 | |
| 0.45.4 | 10 / 0 | |
| 0.45.3 | 10 / 0 | |
| 0.45.2 | 10 / 0 | |
| 0.45.1 | 10 / 0 | |
| 0.45.0 | 10 / 0 | |
| 0.44.8 | 10 / 0 | |
| 0.44.7 | 10 / 0 | |
| 0.44.6 | 10 / 0 | |
| 0.44.5 | 10 / 0 | |
| 0.44.4 | 10 / 0 | |
| 0.44.3 | 10 / 0 | |
| 0.44.2 | 10 / 0 | |
| 0.44.1 | 10 / 0 | |
| 0.44.0 | 10 / 0 | |
| 0.43.5 | 10 / 0 | |
| 0.43.4 | 10 / 0 | |
| 0.43.3 | 10 / 0 | |
| 0.43.2 | 10 / 0 | |
| 0.43.1 | 10 / 0 | |
| 0.43.0 | 10 / 0 | |
| 0.42.4 | 10 / 0 | |
| 0.42.3 | 10 / 0 | |
| 0.42.2 | 10 / 0 | |
| 0.42.1 | 10 / 0 | |
| 0.42.0 | 10 / 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.
v0.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.