awaitly-postgres@36.0.0
PostgreSQL persistence adapter for awaitly workflows
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe static finding is explained by the legitimate runtime bridge to pg and awaitly/durable. There are no lifecycle hooks or indicators of unconsented execution, exfiltration, persistence, or remote payload loading.
Decision evidence
public snapshot- The manifest has no install lifecycle hook and exposes only build, test, lint, and clean scripts.
- The CommonJS entry point only loads pg, awaitly/durable, and crypto.
- Database access is initiated through the exported postgres function with a caller-supplied connection URL.
- The package can create tables and modify snapshot rows in the PostgreSQL database selected by its caller.
- No credential harvesting, filesystem access, shell execution, remote endpoint, or dynamic code execution was found.
Source & flagged code
4 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.cjsView on unpkg · L1The CommonJS entry point only loads pg, awaitly/durable, and crypto.
dist/index.cjsView on unpkg · L1Database access is initiated through the exported postgres function with a caller-supplied connection URL.
dist/index.cjsView on unpkg · L16Findings
Affected versions and remediation
This report applies to awaitly-postgres@36.0.0.
See all versions of awaitly-postgres for other recorded verdicts.
- Review the evidence and your use of awaitly-postgres@36.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.