Open source
Updated
What could become public packages — documented with problem, API sketch, status, and honesty. Profile: github.com/abiralprakash. When a real repo ships, status flips to released with a URL. Nothing here invents a package that isn’t live.
Status legend
candidate — extractable, not published · demo — interactive here · released — public repo URL
candidate · not published yet
Problem: Normalize queries and run exact-first full-text search over register-scale rows without fuzzy latency traps.
API sketch: normalizeQuery(q) · searchExact(db, q, { limit }) · optional expandLater hooks — no silent fuzzy default.
Docs depth: Pattern + decision documented; package extract pending license step from production.
candidate · not published yet
Problem: Typed bindings, migration discipline, and expand-contract schema changes for multi-tenant Workers apps.
API sketch: migration runner wrappers · tenant-scoped query helpers · soft-fail transaction shapes used on NepalIPMS.
Docs depth: Architecture notes live; reusable module not cut out yet.
candidate · not published yet
Problem: Stage OCR output with confidence fields and a review gate before merge to the system of record.
API sketch: stageExtraction(doc) · scoreFields(fields) · requireReview(beforeMerge) — never silent write.
Docs depth: Pipeline diagrams and research notes; library not published.
candidate · not published yet
Problem: Shared error shapes, auth session checks, and request logging across LegalTech APIs without a heavy framework.
API sketch: composeable withErrorBoundary · withSession · JSON error envelope used in production Workers.
Docs depth: Described in engineering notes; not a published starter repo.
candidate · not published yet
Problem: Editorial timeline, matter activity, and deadline lists without dashboard card grids.
API sketch: markup + CSS tokens matching this site’s Newsreader/Inter language — extractable snippets, not an npm design system claim.
Docs depth: Visible on this portfolio; package TBD.
candidate · not published yet
Problem: Client-side related-link graphs for portfolios and internal docs without a CMS.
API sketch: JSON node map → render related rails (as used by this site’s knowledge-graph.json).
Docs depth: Pattern lives in-repo on the portfolio; not published as a standalone package.
demo
Problem: Amortization math for finance widgets — principal, annual rate, term → monthly payment.
Status: Interactive demo on this page. Vanilla JS formula; not an npm package.
Monthly payment: —
demo · public portfolio JS
Problem: Small client patterns — nav drawer, theme toggle, search overlay, freshness labels — already shipped in this site’s /js/.
Status: Source is the public portfolio repo, not a separate package. Document here so extractors know where to look; still not fake npm names.