autotel-drizzle@0.3.9
OpenTelemetry instrumentation for Drizzle ORM
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime implements caller-invoked database tracing without a package-selected network destination. Query text can be included in spans by default, which is expected instrumentation behavior routed through the application's configured telemetry pipeline.
Decision evidence
public snapshot- package.json routes imports to the Drizzle instrumentation entrypoint; its scripts show no install lifecycle hook.
- The inspected dependency manifests and entrypoints expose ordinary OpenTelemetry APIs and trace-context helpers.
- autotel-db provides database-plan helpers and sanitizes plan errors before exporting them as attributes.
- The package wraps caller-provided Drizzle clients and emits query information through OpenTelemetry spans; no package-selected network recipient is established.
- Query-text capture defaults on, and its sanitizer truncates long statements but does not redact their contents, so SQL may reach the application's configured telemetry pipeline.
Source & flagged code
8 flagged · loading sourcepackage.json routes imports to the Drizzle instrumentation entrypoint; its scripts show no install lifecycle hook.
package.jsonView on unpkg · L2package.json routes imports to the Drizzle instrumentation entrypoint; its scripts show no install lifecycle hook.
package.jsonView on unpkg · L64Findings
Affected versions and remediation
This report applies to autotel-drizzle@0.3.9.
See all versions of autotel-drizzle for other recorded verdicts.
- Review the evidence and your use of autotel-drizzle@0.3.9 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.