Open sourcePublic and installableMerged, not proposed

Code

Patches and side projects

Patches sent upstream, and side projects published because they turned out to be useful to someone other than me.

None of this is a product and none of it is anyone's roadmap. The upstream work comes first because it is the part that only counts once it merges — a patch carried in an upstream project is a harder claim than a repository of my own.

The skills encode practice proven at work and then rewritten from scratch as something an agent can run. The rest came from hitting the same gap more than once and getting tired of it.

Upstream

Merged into upstream

Only what actually landed is listed — merged, or imported and merged where the project works that way, or carried in by a maintainer who kept the credit. Proposals that were not accepted are not achievements, and the ones still open are not either.

JavaScript engine mozilla/rhino

ECMAScript in Rhino

Language features implemented in Mozilla's JavaScript engine, and a specification-conformance fix where Rhino preferred array-like objects over iterables and TC39 says otherwise. Some features arrived the other way: a maintainer picked up the work and carried it in, which counts the same once it ships.

Merged

Promise.try Set methods ArrayBuffer transfer Error.isError Math.f16round Array.from conformance

Carried in by a maintainer, crediting this work

Resizable ArrayBuffers and typed arrays WeakRef

JavaScript engine facebook/hermes

Math.sumPrecise in Hermes

Exact floating-point summation for React Native's engine, implemented with compensated summation so a sum of many doubles does not drift. Meta lands contributions by importing them, so the pull request reads closed while the commit carries the authorship — and the feature has been maintained by their engineers since.

Merged

Math.sumPrecise

Landed: Imported and merged; refined afterwards by Meta engineers

Policy engine open-policy-agent/opa

Instrumentation in Open Policy Agent

Instrumentation for a policy engine running in production: a benchmarking harness for the WebAssembly path, a counter for the network calls a policy makes, and documentation for metrics that had none. The project credits contributors by name in its release notes, which is how a fix acquires a date and a version rather than just a merge.

Merged

WASM benchmarking http.send counter Metrics documented

Named in the release notes

v1.9.0 v1.14.0 v1.16.0

CNCF contributor card ↗

Client SDK aws-amplify/amplify-js

Auth and sync fixes in Amplify

Bugs found by running it at scale and fixed upstream: users logged out at random because token clearing was too aggressive, GraphQL sockets that never reconnected after an auth error, and DataStore queries that could not express membership until they could.

Merged

in / notIn operators Random logouts fixed Socket reconnection

Contributions mozilla-ai

any-llm and any-agent at Mozilla AI

Merged into any-llm and any-agent — the model-agnostic client and agent framework Mozilla publishes.

Internet-Drafts anivar/ietf-contributions

IETF contributions

Canonical source for the Internet-Drafts and specification text, with the toolchain that builds them. draft-aravind-oauth-decision-subject defines dsub, naming the party a decision is about; draft-aravind-oauth-operator-of-record defines opr, marking who operated when key binding cannot distinguish a human from an agent acting for one. Section 10.2 of draft-ranjbar-dane-did, Continuity of Holding, was merged in full, with co-authorship from -01.

Drafts: dsub · opr — JWT claims for agent authorization, -00 posted 19 Jul 2026
Co-authored: draft-ranjbar-dane-did — Continuity of Holding, merged in -01
Verifies: Rebuilt text diffed against every posted revision

The drafts →

Skills

Knowledge an agent can run

The experiment: whether an agent follows rules better than it follows documentation. Published on skills.sh, where the install counts say more than I could.

Testing skills skills.sh/anivar

Agent-native test infrastructure

A testing stack proven in production, encoded as rules a coding agent follows rather than documentation it has to interpret: Zod for contracts, Faker for data, Jest for units, Maestro for flows, with MSW and Redux-Saga alongside. Each skill pairs an implementation guide with its testing counterpart.

Skills: zod · zod-testing · jest · msw · redux-saga · redux-saga-testing
Stack: Zod for contracts · Faker for data · Jest for units · Maestro for flows

Authoring skill anivar/developer-docs-framework

Diátaxis, made enforceable

Diátaxis as something enforceable rather than aspirational: the four documentation modes with rules an agent applies while writing, and style guides it checks itself against.

Basis: Diátaxis — tutorial, how-to, reference, explanation
Enforces: Rule set and style guides, applied during authoring

Install as a skill ↗

Review skill anivar/contributor-codebase-analyzer

Reading a codebase before contributing

The deep read a reviewer needs before touching unfamiliar code: what a contribution actually changes, which conventions the repository already holds, and where the change sits against them — done as analysis rather than as a diff summary.

Reads: Repository conventions, contribution history, change surface

Install as a skill ↗

Skill · schema anivar/corrigibility-schema

Corrigibility assessment

The framework as something an agent installs and runs: the assessment schema packaged so a system can be scored against the five conditions without reading the paper first.

Protocol: corrigibility-schema — manifest and audit, RFC 8785 canonical, Ed25519 signed
Paper: Corrigibility as a Structural Precondition — doi 10.2139/ssrn.6059075

The framework → Install as a skill ↗

Skill · package anivar/india-tax-guru

India income-tax toolkit

A computation engine rather than a chat assistant: every figure it reports traces to a function, and every rule is versioned by assessment year so nothing drifts silently across Budgets. Old-versus-new regime comparison, HRA and capital-gains computation, CTC restructuring, and the advance-tax interest nobody enjoys estimating by hand. Installable as a Python package or as an agent skill that reads the documents and asks only what they cannot answer.

Computes: Regime comparison · HRA · capital gains · house property · 234B/234C interest
Ships as: Python package on PyPI, with a CLI — and the same engine as an agent skill
Licence: MIT

PyPI ↗ Install as a skill ↗

Published

Written here, and given away

A package written because the workaround stopped being funny the third time, and a rebuild done for a campaign that needed infrastructure more than it needed another volunteer.

Published package anivar/amplify-watermelondb-adapter

WatermelonDB adapter for Amplify DataStore

Amplify's DataStore loads its whole dataset into memory, which stops being viable once an offline app's data outgrows the phone. This swaps the storage engine for WatermelonDB, so queries stay reactive and rows load lazily. The upstream half — modernising the Expo SQLite adapter alongside it — is proposed and still open.

Upstream: aws-amplify/amplify-js — adapter proposal

Open upstream PR ↗

Rebuilds rethinkaadhaar.in

Campaign infrastructure, pro bono

A campaign site rebuilt as maintainable static infrastructure: content recovered verbatim from a decade of exports, an editor's CMS that non-technical staff can actually publish from, and CI that catches a broken build before a volunteer sees it.

Rebuilt: rethinkaadhaar.in
Stack: Astro · Decap CMS · auth worker · deploy gates

The rest, including the abandoned experiments, is on GitHub; the skills install from skills.sh/anivar. The papers, drafts and the applied record are on the research page.