Skip to main content

A decade of learning where anyone could inspect the work.

Not a wall of repositories — the progression from complete applications to developer tools, product platforms, external contribution, and public infrastructure.

5,972
GitHub stars
Across 61 public, non-fork repositories owned by tortuvshin and intelligo-mn
1,212
Forks received
Repository forks received across the same public source set
12,649
Public GitHub contributions
Public contribution-calendar activity since 2014
149
Public authored pull requests
Public repositories only; private work is excluded
21
Independently maintained npm packages
Personal, Intelligo, dev.mn, and Grove families only
1,869,096
Cumulative npm downloads
Official API total from first publication through 2026-07-21; not unique users

Currently maintained

Intelligo

Open-source application infrastructure for AI products.

An open-source Next.js framework for vertical AI SaaS — sign-up, workspaces, plans, credits, per-run cost, audit and an admin console. The pages install into your repo as source, the engine under them is npm packages you upgrade, and your agent framework stays untouched.

Grove

A file-first framework for curated directories and structured knowledge.

A file-first publishing system. YAML records and Markdown in a git repository become a searchable static site plus every output around it — sitemap, JSON-LD, OG images, JSON datasets, llms.txt — and scheduled syncs flag the entries that quietly stopped being true.

Open App Scout

A curated directory of production-ready open-source applications.

A hand-picked directory of production open-source applications — not tutorials, boilerplates or libraries. Every app is one reviewed YAML record; weekly jobs refresh GitHub metadata through pull requests, and a monthly sweep queues stale entries for a person to decide on.

Contribution history

  1. 2016–2017

    Complete applications were the curriculum

    I learned by running and tracing whole PHP, Java, Android, and Node.js applications. Full systems exposed boundaries, data flow, and failure in a way tutorials could not.

  2. 2017–2019

    Intelligo: from API to developer product

    A Messenger framework that grew documentation, examples, tests, and a CLI. The main package has 643,422 downloads; the five-package historical family reached 1,384,024 through 2026-07-21.

  3. 2017–2019

    Neuro.js: applied ML before the current AI wave

    Classification and learning for assistants in the browser and in Node.js — a companion layer beside the framework, not a generic claim that Intelligo “had AI.”

  4. 2019–2021

    The framework became a visual product

    The third generation moved up the stack into a drag-and-drop chatbot builder with an API, a simulator, and a studio, over a 2,195-commit history. I led it and remain the dominant human contributor; I was not the only one. That repository was reused for the 2026 framework, so the builder’s history is no longer at its original address.

  5. 2023–2024

    Fleetbase tested the method in somebody else’s system

    I entered an unfamiliar logistics OSS stack and authored 46 pull requests across ten repositories; forty were merged. The work crossed SDKs, release tooling, storefront, mobile, Laravel, and Ember surfaces.

  6. 2017 → 2026

    Open App Scout productized the way I learn

    A curated list became a structured directory of complete open-source applications. Its 4,334 stars carry the repository’s full history; they did not appear after the 2026 product rebuild.

  7. 2026

    Grove extracted the repeated maintenance problem

    Schemas, imports, validation, review workflows, and release tooling came out of Open App Scout into core, CLI, Astro, and Starlight packages, with the UI shipped as a registry that installs as source. External adoption is the evidence still missing.

  8. 2026

    Intelligo came back as a framework for AI SaaS

    The name returned for a different problem: everything around an AI agent — sign-up, workspaces, plans, credits, per-run cost, audit, and an admin console. It was extracted from a career advisor after seven months in a private repository, and first published on 2026-08-29 under Apache-2.0.

How the totals are scoped

Repositories
Public, non-fork repositories owned by tortuvshin and intelligo-mn, at the 2026-07-22 snapshot.
GitHub totals
Contribution and pull-request counts exclude restricted and private activity.
npm packages
npm lists 53 packages where I am a maintainer. The 21 counted above are the independently maintained personal, Intelligo, dev.mn, and Grove families only.
Downloads
Cumulative through 2026-07-21. Maintainer status is not sole authorship, and downloads are not unique users.

The honest reading

Some projects found adoption. Some were abandoned. Some architectures grew before demand justified them.

The record still compounds: applications became libraries; libraries became products; product pain became infrastructure; and the learning returned to professional systems.