owletto
Unified CLI for Lobu memory — dev, deploy, and manage from one command
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:shady-links-raw-ip | AI (semgrep): Raw IPs are localhost/127.0.0.1 loopback addresses used for local OAuth redirect URIs — not exfiltration endpoints. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in a Gmail connector for email body parsing is standard and expected. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used in scrypt-based secret verification — legitimate cryptographic pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 1 / 6 | |
| 1.3.0 | 1 / 6 | |
| 1.2.0 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.0 | 5 / 2 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.