@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ridit/ink-ui | AI (dependencies): Same-org sibling package from monorepo split. | ai | |
| dependencies | unvetted-dep:@ridit/lens-core | AI (dependencies): Same-org sibling package from monorepo split. | ai | |
| phantom-deps | phantom-dep:bun | AI (phantom-deps): Bun runtime used for build scripts, referenced in config. | ai | |
| source-diff | encoded-string-file:dist/index.mjs | AI (source-diff): Bundled unicode data table (JSON.parse) from Parcel build, not hidden payload. | ai | |
| phantom-deps | phantom-dep:add | AI (phantom-deps): Used in build/config tooling, not a security concern. | 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:child-process-import | AI (semgrep): CLI tool that runs user commands; child_process usage is core to its functionality. | 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 | |
| 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 |
Versions (showing 35 of 35)
| 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.4.1 | 9 / 3 | |
| 0.4.0 | 9 / 3 | |
| 0.3.9 | 9 / 3 | |
| 0.3.8 | 14 / 5 | |
| 0.3.7 | 14 / 5 | |
| 0.3.6 | 14 / 5 | |
| 0.3.5 | 14 / 5 | |
| 0.3.4 | 14 / 5 | |
| 0.3.3 | 15 / 5 | |
| 0.3.2 | 15 / 5 | |
| 0.3.1 | 15 / 5 | |
| 0.3.0 | 15 / 5 | |
| 0.2.9 | 15 / 5 | |
| 0.2.8 | 15 / 5 | |
| 0.2.6 | 15 / 5 | |
| 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.3.8
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.