Skip to content

docs: document security posture #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
slegarraga merged 1 commit into from
Jun 5, 2026
Merged

docs: document security posture #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,9 @@

> Normalize OpenAI, Anthropic and Gemini API errors into one shape: category, retryable flag and `Retry-After` delay. **Zero dependencies.**

Security posture is tracked in [docs/security-posture.md](./docs/security-posture.md),
including CodeQL, OpenSSF Scorecard, Dependabot and branch rules.

Every LLM provider fails differently. OpenAI nests `{ error: { type, code, param } }`, Anthropic wraps `{ type: "error", error: { type } }`, Gemini speaks Google RPC status strings, and each puts retry hints in a different place. `llm-errors` collapses all of that into a single, predictable object so your retry and error-handling code stays provider-agnostic.

```ts
Expand Down
20 changes: 20 additions & 0 deletions docs/security-posture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Security posture

`llm-errors` is a zero-runtime-dependency package, but the repository still
tracks supply-chain controls as part of maintenance.

Current controls:

- MIT license and public security policy.
- GitHub vulnerability alerts and Dependabot security updates.
- Secret scanning and push protection.
- CI on Node 20 and 22.
- CodeQL analysis for JavaScript/TypeScript.
- OpenSSF Scorecard workflow with published results.
- Pinned GitHub Actions and least-privilege workflow permissions.
- Branch ruleset for `main` requiring CI and CodeQL checks before merge.
- CODEOWNERS for maintainer review visibility.

Security reports should not be opened as public issues. Use the process in
[SECURITY.md](../SECURITY.md) or contact
[sebastian@0a.cl](mailto:sebastian@0a.cl).