@ridit/lens
Understand your codebase.
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool that runs user commands; child_process usage is core to its functionality. | ai | |
| phantom-deps | phantom-dep:sugar-high | AI (phantom-deps): Declared dep used in config/build context; phantom-dep heuristic false positive for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into a child_process spawn call to inherit environment is standard CLI practice, not a secret leak. | ai | |
| phantom-deps | phantom-dep:react-devtools-core | AI (phantom-deps): react-devtools-core is declared as a runtime dep and explicitly externalized in the build script; not directly imported by design. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.4.8 | 8 / 2 | |
| 0.4.7 | 8 / 2 | |
| 0.4.6 | 8 / 2 | |
| 0.4.5 | 8 / 2 | |
| 0.4.4 | 8 / 2 | |
| 0.4.3 | 8 / 2 | |
| 0.4.2 | 7 / 2 | |
| 0.2.5 | 12 / 3 | |
| 0.2.4 | 10 / 2 | |
| 0.2.2 | 9 / 2 | |
| 0.2.1 | 9 / 2 | |
| 0.2.0 | 9 / 2 | |
| 0.1.9 | 9 / 2 | |
| 0.1.8 | 9 / 2 | |
| 0.1.7 | 9 / 2 | |
| 0.1.6 | 10 / 2 | |
| 0.1.5 | 10 / 2 | |
| 0.1.4 | 9 / 2 | |
| 0.1.1 | 9 / 2 | |
| 0.1.0 | 9 / 2 |
v0.4.8
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
2 findingsSpreading entire process.env into an object — may capture all secrets 83 | cwd, 84 | shell: true, > 85 | env: { ...process.env, FORCE_COLOR: "1" }, 86 | stdio: ["pipe", "pipe", "pipe"], 87 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | shell: true, > 92 | env: { ...process.env }, 93 | }); 94 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.