@netlify/serverless-functions-api@2.25.1
⚠ Under reviewThe runtime API for Netlify Functions
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe flagged command is used by the host resource detector, and the inspected exporter logs spans to console rather than sending them to an unrelated endpoint. I cannot certify clean because the required @netlify/types main file is empty and the citation service cannot issue a valid citation for it.
Decision evidence
public snapshot- The manifest routes the package root, server API, and instrumentation subpath to the inspected runtime files.
- The package’s prepare script sets up Husky hooks; its published lifecycle scripts do not show a registry install hook.
- The server entry handles requests through the selected function handler.
- The instrumentation bundle’s host detector reads a platform machine identifier, consistent with host resource detection.
- Its trace exporter serializes spans to console output; the instrumentation starts an SDK with header collection skipped and Netlify service metadata.
- The inspected @netlify/types manifest has no install lifecycle script.
- The declared @netlify/types main file was empty. The citation service could not issue an exact citation for an empty file, so required clean citation coverage could not be completed.
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.1.
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.1 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.