Visit my portfolio ↗ · LinkedIn · Email
I’m Aman Awasthi, a software builder studying Banking & Finance in India.
Alongside my B.Com (Hons.) and CA Foundation preparation, I work on developer tools, browser applications and Linux systems.
I like work where the details matter: a command that previews its changes, an error that explains what happened, a fix someone else can review.
I help maintain opencode-mem and awesome-free-apps, and contribute fixes and tests to developer tools.
13 merged pull requests across 6 external repositories, verified on September 12, 2026 for the preceding 12 months. Browse the contribution record →
| Project | Selected merged work |
|---|---|
| opencode-mem | Reduce storage overhead for new vector indexes, preserve provider parameters, and show matched-memory counts. |
| Inversify | Validate OpenAPI base-URI declarations and support discriminated errors in HTTP error filters. |
| awesome-free-apps | Make link audits detect HTTP failures, limit concurrency, and return meaningful exit statuses. |
| svg2pdf.js | Align PDF link hitboxes with rendered SVG elements. |
| jest-codemods | Preserve TypeScript this parameters during migration. |
| RTK | Add regression coverage for anchored command-filter patterns. |
Proposed contributions awaiting review
- RTK #3755: Windows Python test-launcher routing.
- tensorflow-onnx #2487: Keras 3 model-output mapping and save/load regression coverage.
These pull requests were open, not merged, when this profile was updated on September 12, 2026.
An experimental Void Linux system with installation, setup and software-management tools.
Rust · C · Svelte · Tauri · Linux
Installs and organizes skills, prompts and MCP configurations for AI workflows.
TypeScript · Node.js
A browser toolbox for document, image, media and everyday utility tasks.
React · TypeScript · Vite
Organizes files from the terminal, with dry-run previews and undo manifests.
Python · Typer · Rich
View all work on my portfolio →
Understand the failure. Reproduce it before changing the implementation.
Make the fix reviewable. Keep changes focused and add regression coverage where it helps.
Leave a clear trail. Document actual behavior, explain failures and make changes reversible.
- Linux desktop latency: find the cause before tuning
- Privacy-first React components: storage and safe defaults
- Using an AI coding CLI: context, permissions and diff review
Have something in mind? Tell me about it →



