OpenAI SDK (JS)
npmopenaiThe official OpenAI JavaScript SDK for Node.js and browser environments. It is used in Next.js applications, Vercel AI SDK integrations, and serverless API routes that proxy OpenAI model calls. The SDK reads `OPENAI_API_KEY` from environment variables and handles streaming, function calling, and batch requests.
Checking OpenAI SDK (JS)
openai 4.56.0 is a clean, monitored version with no known supply chain compromise. The example response returns supply_chain_monitored: true and compromised: false with an empty sources array.
curl "https://api.attestd.io/v1/check?product=openai&version=4.56.0" \
-H "Authorization: Bearer YOUR_API_KEY"{
"product": "openai",
"version": "4.56.0",
"supported": true,
"risk_state": "none",
"risk_factors": [],
"actively_exploited": false,
"remote_exploitable": false,
"authentication_required": false,
"patch_available": false,
"fixed_version": null,
"confidence": 0.9,
"cve_ids": [],
"cves": null,
"max_epss": null,
"typosquat": null,
"supply_chain_monitored": true,
"supply_chain": {
"compromised": false,
"sources": [],
"malware_type": null,
"description": null,
"advisory_url": null,
"compromised_at": null,
"removed_at": null
},
"last_updated": "2026-05-01T00:00:00Z"
}Why this package is monitored
The OpenAI JS SDK resolves OPENAI_API_KEY as soon as the client module initializes in Node or edge routes. Tampering at that point can steal the key and stream or completion payloads without changing the visible API surface.
Attestd monitors openai using the following detection sources:
registryManually curated advisories in the Attestd registry, verified by a human analyst. Confidence 1.0.
osvOSV.dev malicious-package advisories with IDs prefixed MAL-. Confidence 0.95.
npm_deprecationnpm package versions with deprecation messages containing targeted attack language such as malicious, backdoor, or compromised. Confidence 0.80.