01
Close to the metal
Operating-system kernels, C internals, custom shells and an IDE built from the ground up. The projects here exist to make the machine legible rather than to hide it.
Open source since 2022
Transforming Computing.
ni_sh_a.char is an open-source organisation that builds the layers most people never see — kernels and compilers, developer automation, AI assistants, security tooling and Android apps. Every line of it is public, readable and open to contribution.
—
Public projects
—
Stars earned
—
Languages
—
Live demos
// The index
Every public repository, always current.
This list is generated straight from the GitHub API and refreshes on a schedule — anything the organisation publishes shows up here on its own. Open a project to read an AI-written breakdown of what it is, why it exists and when you would reach for it.
// About
Systems work, done in the open.
The organisation started in April 2022 as a place to put research code where other people could actually use it. It has stayed that way: no private drops, no marketing-first releases — the repository is the product.
02
Tools that remove toil
Automation for the parts of development nobody enjoys — environment bootstrapping, containerised workflows, release pipelines and API scaffolding, packaged so they run the same on any machine.
03
Applied intelligence
Virtual assistants, bioinformatics notebooks, computer-vision experiments and autonomous agents — research code kept honest by being shipped, documented and left open to inspection.
// Contribute
The best contribution is an issue.
Genuinely — before a pull request, before a fork, open an issue. A bug you hit, a README that made no sense, a feature you wanted, a question that went unanswered: all of it is useful, and none of it needs you to write a single line of code. Issues are read, and they are answered.
STEP 01
Say what happened
Open an issue on the repository in question. Describe what you expected, what you got, and the version or commit you were on. Screenshots and stack traces are welcome. Pick a repository ↗
STEP 02
Claim it, or don't
If you want to fix it yourself, say so in the issue and it is yours. If you'd rather just report and move on, that is a complete contribution — reporting a real bug is worth more than a drive-by patch.
STEP 03
Open the pull request
Fork, branch, keep the diff focused on the issue, and link it in the description. Small and reviewable beats large and complete. Questions mid-way belong in the issue thread, not in your head.
// Contact
Get in touch.
Something wrong with a project?
Use the issue tracker. It's public, it's searchable, and it means the next person with your problem finds the answer instead of asking again. This is the fastest route to a fix.
Open an issueAnything else
Collaboration, security disclosures, or a question that doesn't belong in a public thread — email works. Please keep bug reports on GitHub so they stay findable.
piyushmishra.professional@gmail.com