@netlify/serverless-functions-api@2.26.0
The runtime API for Netlify Functions
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe flagged command execution belongs to host resource detection, and the telemetry exporter writes to the runtime console under a Netlify-specific marker. The telemetry behavior is tied to an explicit import, and the inspected lifecycle and runtime sources establish no concrete attack chain.
Decision evidence
public snapshot- The manifest exposes telemetry as a separate import path and exports the server runtime entry.
- The package's prepare hook sets up Husky; prepublishOnly runs npm ci and tests. No install hook is declared.
- The inspected @netlify/types manifest declares build and test scripts but no install lifecycle hook.
- The server entry starts from Netlify runtime configuration and loads its configured function entry.
- The telemetry module detects host resources and reads the OS machine identifier as a host attribute.
- When imported, the telemetry module starts its SDK and writes serialized spans to the console with a Netlify-specific marker; its fetch instrumentation skips headers.
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.26.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.26.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.