awaitly-postgres@35.0.0
PostgreSQL persistence adapter for awaitly workflows
AI Security Review
scanned 1mo ago · by lpm-firewall-aiDirect inspection shows a compact PostgreSQL adapter with no lifecycle execution or hostile primitives. The scanner's dependency-bridge signal is explained by declared pg and awaitly dependencies.
Decision evidence
public snapshot- The published entrypoint imports pg and awaitly/durable, consistent with a PostgreSQL workflow adapter.
- The manifest declares only normal development scripts and no install lifecycle hook.
- No child-process, shell, eval, filesystem-harvesting, or HTTP client behavior appears in the published entrypoints.
- Database connections and schema creation occur only after the caller invokes postgres().
- The code performs parameterized PostgreSQL snapshot and lock operations; no external network endpoint is embedded.
Source & flagged code
3 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.cjsView on unpkg · L1The published entrypoint imports pg and awaitly/durable, consistent with a PostgreSQL workflow adapter.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to awaitly-postgres@35.0.0.
See all versions of awaitly-postgres for other recorded verdicts.
- Review the evidence and your use of awaitly-postgres@35.0.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.