openai
The official TypeScript library for the OpenAI API
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Signals reflect a deliberate namespace placeholder stub for the official OpenAI SDK, not a spam or malicious package. Age, version count, and publisher track record confirm legitimacy. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): [email protected] is a long-standing namespace reservation stub (2113 days old, 354 versions in registry); the 0.0.0 version is not indicative of malicious intent here. | ai | |
| phantom-deps | phantom-dep:@types/qs | AI (phantom-deps): TypeScript @types packages are conventionally declared as deps without direct imports; stable pattern for the openai SDK. | ai | |
| dependencies | unvetted-dep:@types/qs | AI (dependencies): @types/qs is a standard TypeScript type definition package used alongside the qs runtime dep; no security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official OpenAI SDK with long history and strong ecosystem trust; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): OpenAI is migrating maintainer accounts from personal to org-scoped npm accounts (e.g., fouad → fouad-openai). This pattern is consistent across their releases and is not indicative of a takeover. | ai | |
| dependencies | unvetted-dep:node-fetch | AI (dependencies): node-fetch is a standard HTTP client; legitimate dependency for API client library. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type definitions loaded by convention in TypeScript packages; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/node-fetch | AI (phantom-deps): Type definitions loaded by convention in TypeScript packages; stable for this package. | ai | |
| source-diff | obfuscated-file:resources/realtime/realtime.d.ts | AI (source-diff): TypeScript declaration file with verbose JSDoc comments for Realtime API types; long lines are type definitions, not obfuscation. False positive for this SDK. | ai | |
| source-diff | obfuscated-file:resources/realtime/realtime.d.mts | AI (source-diff): TypeScript declaration file with verbose JSDoc comments for Realtime API types; long lines are type definitions, not obfuscation. False positive for this SDK. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): All new maintainers (easong-openai, aibrahim-openai, apcha-oai, victor-openai, seratch-openai, gabor-openai) follow OpenAI's internal account naming convention. Consistent with team expansion. | ai | |
| provenance | publisher-changed | AI (provenance): All publisher/maintainer accounts follow the *-openai naming convention, consistent with OpenAI's internal team rotation. Legitimate organizational handoff pattern for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The IP 169.254.169.254 is the Azure IMDS endpoint for managed identity token acquisition — a documented, standard Azure cloud integration pattern in the OpenAI SDK's auth module. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of embedding vectors is legitimate API client functionality; no malicious intent. | ai |
Versions (showing 42 of 342)
| Version | Deps | Published |
|---|---|---|
| 4.12.0 | 8 / 0 | |
| 4.11.1 | 8 / 0 | |
| 4.11.0 | 8 / 0 | |
| 4.10.0 | 8 / 0 | |
| 4.9.1 | 8 / 0 | |
| 4.9.0 | 8 / 0 | |
| 4.8.0 | 8 / 0 | |
| 4.7.1 | 8 / 0 | |
| 4.7.0 | 8 / 0 | |
| 4.6.0 | 8 / 0 | |
| 4.5.0 | 8 / 0 | |
| 4.4.0 | 8 / 0 | |
| 4.3.1 | 8 / 0 | |
| 4.3.0 | 8 / 0 | |
| 4.2.0 | 8 / 0 | |
| 4.1.0 | 8 / 0 | |
| 4.0.1 | 8 / 0 | |
| 4.0.0 | 8 / 0 | |
| 3.3.0 | 2 / 2 | |
| 3.2.1 | 2 / 2 | |
| 3.2.0 | 2 / 2 | |
| 3.1.0 | 2 / 2 | |
| 3.0.1 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.0.5 | 2 / 2 | |
| 2.0.4 | 2 / 2 | |
| 2.0.2 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.1.1 | 2 / 9 | |
| 1.1.0 | 2 / 9 | |
| 1.0.0 | 3 / 10 | |
| 0.0.9 | 3 / 10 | |
| 0.0.8 | 3 / 10 | |
| 0.0.7 | 3 / 10 | |
| 0.0.6 | 3 / 10 | |
| 0.0.5 | 3 / 9 | |
| 0.0.4 | 3 / 9 | |
| 0.0.3 | 3 / 9 | |
| 0.0.2 | 3 / 9 | |
| 0.0.1 | 1 / 10 | |
| 0.0.0 | 0 / 0 |
v4.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.