autotel-adapters@2.0.29
Framework adapters and composable DX helpers for autotel
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook and ties the Cloudflare entrypoint to the package’s own adapter bundle. The flagged dependency bridge resolves to declared dependencies and local modules, and the inspected runtime code performs request tracing and logging rather than a concrete attack.
Decision evidence
public snapshot- package.json identifies the package and maps its Cloudflare export to the inspected dist bundle.
- The manifest declares autotel and autotel-edge dependencies; the Cloudflare bundle requires those package dependencies and local integration/core modules.
- The manifest scripts are build, development, type-check, lint, test, and clean tasks; no install lifecycle hook is declared.
- The Cloudflare adapter wraps a caller-provided handler in request tracing, while core logging requires an active trace context.
Source & flagged code
9 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/cloudflare.cjsView on unpkg · L3The manifest declares autotel and autotel-edge dependencies; the Cloudflare bundle requires those package dependencies and local integration/core modules.
dist/cloudflare.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to autotel-adapters@2.0.29.
See all versions of autotel-adapters for other recorded verdicts.
- Review the evidence and your use of autotel-adapters@2.0.29 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.