@netlify/serverless-functions-api@2.25.0
⚠ Under reviewThe runtime API for Netlify Functions
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected lifecycle scripts and runtime excerpts do not establish a concrete attack. However, the dependency manifest declares a main file that could not be read, preventing the required dependency-source coverage; manual review is appropriate while that source is unresolved.
Decision evidence
public snapshot- The package entrypoints expose the main API, server API, and a separate instrumentation module; its prepare hook installs repository Husky hooks.
- The instrumentation module reads a machine identifier through platform-specific commands and starts OpenTelemetry tracing when loaded.
- The declared @netlify/types dependency describes itself as TypeScript definitions and has no install lifecycle scripts, but its declared main file could not be read.
- The server bundle contains ordinary request and event handler selection logic.
- The instrumentation source shows service and Netlify site attributes used to initialize tracing.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/telemetry/instrumentation.jsView on unpkg · L13Findings
Affected versions and remediation
This report applies to @netlify/serverless-functions-api@2.25.0.
See all versions of @netlify/serverless-functions-api for other recorded verdicts.
- Review the evidence and your use of @netlify/serverless-functions-api@2.25.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.