@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 630)
| Version | Deps | Published |
|---|---|---|
| 0.41.8 | 10 / 0 | |
| 0.41.7 | 10 / 0 | |
| 0.41.6 | 10 / 0 | |
| 0.41.5 | 10 / 0 | |
| 0.41.4 | 10 / 0 | |
| 0.41.3 | 10 / 0 | |
| 0.41.2 | 10 / 0 | |
| 0.41.1 | 10 / 0 | |
| 0.41.0 | 10 / 0 | |
| 0.40.9 | 10 / 0 | |
| 0.40.8 | 10 / 0 | |
| 0.40.7 | 10 / 0 | |
| 0.40.6 | 10 / 0 | |
| 0.40.5 | 10 / 0 | |
| 0.40.4 | 10 / 0 | |
| 0.40.3 | 10 / 0 | |
| 0.40.2 | 10 / 0 | |
| 0.40.1 | 10 / 0 | |
| 0.40.0 | 10 / 0 | |
| 0.39.0 | 10 / 0 | |
| 0.38.9 | 10 / 0 | |
| 0.38.8 | 10 / 0 | |
| 0.38.7 | 10 / 0 | |
| 0.38.6 | 10 / 0 | |
| 0.38.5 | 10 / 0 | |
| 0.38.4 | 10 / 0 | |
| 0.38.3 | 10 / 0 | |
| 0.38.2 | 10 / 0 | |
| 0.38.1 | 10 / 0 | |
| 0.38.0 | 10 / 0 | |
| 0.37.13 | 10 / 0 | |
| 0.37.12 | 10 / 0 | |
| 0.37.11 | 10 / 0 | |
| 0.37.10 | 10 / 0 | |
| 0.37.9 | 10 / 0 | |
| 0.37.8 | 10 / 0 | |
| 0.37.7 | 10 / 0 | |
| 0.37.6 | 10 / 0 | |
| 0.37.5 | 10 / 0 | |
| 0.37.4 | 10 / 0 | |
| 0.37.3 | 10 / 0 | |
| 0.37.2 | 10 / 0 | |
| 0.37.1 | 10 / 0 | |
| 0.37.0 | 10 / 0 | |
| 0.36.7 | 10 / 0 | |
| 0.36.6 | 10 / 0 | |
| 0.36.5 | 10 / 0 | |
| 0.36.4 | 10 / 0 | |
| 0.36.3 | 10 / 0 | |
| 0.36.2 | 10 / 0 | |
| 0.36.1 | 10 / 0 | |
| 0.36.0 | 10 / 0 | |
| 0.35.10 | 10 / 0 | |
| 0.35.9 | 10 / 0 | |
| 0.35.8 | 10 / 0 | |
| 0.35.7 | 10 / 0 | |
| 0.35.6 | 10 / 0 | |
| 0.35.5 | 10 / 0 | |
| 0.35.4 | 10 / 0 | |
| 0.35.3 | 10 / 0 | |
| 0.35.2 | 10 / 0 | |
| 0.35.1 | 10 / 0 | |
| 0.35.0 | 10 / 0 | |
| 0.34.14 | 10 / 0 | |
| 0.34.13 | 10 / 0 | |
| 0.34.12 | 10 / 0 | |
| 0.34.11 | 10 / 0 | |
| 0.34.10 | 10 / 0 | |
| 0.34.9 | 10 / 0 | |
| 0.34.8 | 10 / 0 | |
| 0.34.7 | 10 / 0 | |
| 0.34.6 | 10 / 0 | |
| 0.34.5 | 10 / 0 | |
| 0.34.4 | 10 / 0 | |
| 0.34.3 | 10 / 0 | |
| 0.34.2 | 10 / 0 | |
| 0.34.1 | 10 / 0 | |
| 0.34.0 | 10 / 0 | |
| 0.33.12 | 10 / 0 | |
| 0.33.11 | 10 / 0 | |
| 0.33.10 | 10 / 0 | |
| 0.33.9 | 10 / 0 | |
| 0.33.8 | 10 / 0 | |
| 0.33.7 | 10 / 0 | |
| 0.33.6 | 10 / 0 | |
| 0.33.5 | 10 / 0 | |
| 0.33.4 | 10 / 0 | |
| 0.33.3 | 10 / 0 | |
| 0.33.2 | 10 / 0 | |
| 0.33.1 | 10 / 0 | |
| 0.33.0 | 10 / 0 | |
| 0.32.2 | 10 / 0 | |
| 0.32.1 | 10 / 0 | |
| 0.32.0 | 10 / 0 | |
| 0.31.6 | 10 / 0 | |
| 0.31.5 | 10 / 0 | |
| 0.31.4 | 10 / 0 | |
| 0.31.3 | 10 / 0 | |
| 0.31.2 | 10 / 0 | |
| 0.31.1 | 10 / 0 |
v0.41.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.