@lobu/owletto-openclaw
Lobu memory plugin for OpenClaw
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known maintainer manual publish for a deprecation shim; no behavior change. | ai | |
| dependencies | unvetted-dep:@lobu/openclaw-plugin | AI (dependencies): Same-scope successor package, this is a deprecation redirect. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; consistent with legitimate automation setup. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 1 / 0 | |
| 6.0.0 | 0 / 4 | |
| 5.0.0 | 0 / 4 | |
| 4.3.0 | 0 / 4 | |
| 4.2.0 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.1 | 0 / 4 | |
| 3.0.2 | 0 / 2 | |
| 3.0.1 | 1 / 2 | |
| 1.7.0 | 0 / 4 | |
| 1.6.0 | 0 / 2 | |
| 1.5.0 | 0 / 2 | |
| 1.4.0 | 0 / 2 |
v6.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: buremba.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (buremba) than the most recent previously approved version (GitHub Actions) on 2026-05-04, but buremba is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.