@lobu/connector-worker
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): sharp is a known optional native binding; not directly imported but used at runtime. | ai | |
| phantom-deps | phantom-dep:jimp | AI (phantom-deps): jimp is a runtime image-processing dep referenced in config; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:playwright | AI (phantom-deps): playwright aliased via npm alias (patchright); config-referenced, not directly imported. | ai | |
| phantom-deps | phantom-dep:playwright-vanilla | AI (phantom-deps): playwright-vanilla is an npm alias for playwright; config-referenced, not directly imported. | ai | |
| phantom-deps | phantom-dep:@xenova/transformers | AI (phantom-deps): ML embedding dep referenced in config; runtime-loaded, stable false positive. | ai | |
| phantom-deps | phantom-dep:@lobu/worker | AI (phantom-deps): Same-org monorepo dep; phantom-dep is a stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 9.3.0 | 9 / 3 | |
| 7.1.0 | 9 / 3 | |
| 7.0.0 | 7 / 3 | |
| 6.1.1 | 7 / 3 | |
| 6.0.1 | 6 / 3 |
v9.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.