@netlify/serverless-functions-api@2.28.0
The runtime API for Netlify Functions
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe suspicious scanner signals resolve to OpenTelemetry instrumentation and a platform-specific machine ID detector, with no evidence connecting the detector output to exfiltration or unrelated execution. The package’s explicit instrumentation export and configurable OTEL endpoint fit its stated runtime API purpose.
Decision evidence
public snapshot- The package is described as Netlify Functions’ runtime API and explicitly exports a separate OpenTelemetry instrumentation entry point.
- The instrumentation initializes OpenTelemetry tracing and includes function URL and Netlify site attributes, consistent with runtime observability.
- The flagged command execution reads the macOS platform UUID as part of a machine ID detector; the reviewed code shows no connection from that result to an outbound request.
- The OpenTelemetry exporter reads its endpoint from standard OTEL environment configuration.
Source & flagged code
9 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.28.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.28.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.