Open source

Published code, and the discipline that comes with publishing it.

Everything public on this GitHub account that has code in it: what each repository is, the licence it ships under, where it is published, and what the tree actually carries. Read from the GitHub API rather than typed out by hand.

There are no star counts on this page. These repositories were published between 2024 and 2026 and none has an adoption history worth quoting yet — the licence, the packaging, the CI and the governance are the parts that are verifiable today, so those are what is shown.

5
public repositories with code
2
primary languages
3
under an OSI-approved licence
0
package registries published to

Repositories — most recently pushed first

What “open source” means on this account.

Research software engineering postings ask for open-source Python packaging, project governance and reproducible harnesses by name. These are the ones that exist in the repositories above, not a list of things worth doing some day.

Licensing & citation

  • Apache-2.0
  • MIT
  • CITATION.cff
  • Semantic versioning

Packaging & distribution

  • PyPI packaging
  • npm publishing
  • Container publishing (ghcr.io)
  • uv

Governance

  • CODEOWNERS
  • GOVERNANCE.md
  • SECURITY policy
  • Code of Conduct
  • CONTRIBUTING.md

Verification

  • GitHub Actions CI
  • codecov
  • OpenSSF Scorecard
  • pre-commit
  • Benchmark harness design

Documentation

  • mkdocs sites
  • devcontainers
  • Reproducible harnesses

How to read this page

What is left out
Forks. Most of the repositories on the account are forks of other people’s projects — PyTorch, DSPy, openai-agents-js — kept for reading and patching. Listing them as his open-source work would be a misrepresentation, so they are filtered on the API’s fork field. Also excluded: the profile README repository, and repositories created but never pushed to.
Why no stars
A star count measures how many people have found a repository, and a repository published a few weeks ago has not been found by anyone. It says nothing about whether the code is licensed, packaged, tested or citable — which is the entire question a reviewer is trying to answer. Adoption work is the honest gap in this record, and it is being worked on rather than papered over.
Where the data comes from
The GitHub REST API, /users/bhaskargurram-ai/repos, unauthenticated and fetched on the server, cached for six hours. Language, licence, description, topics and dates are GitHub’s. Registries, governance files and the notes under each description are from profile/master-profile.yaml and each repository’s own tree. If the API fails, the page serves a dated snapshot and labels it.
Credit
The idea of building a portfolio page out of a live GitHub account comes from masterPortfolio by Ashutosh Hathidara (MIT licence, © 2020). The idea is all that was taken — none of its code is used here, and its stars-and-followers framing is deliberately inverted for the reasons above.
Case studies behind these →The papers they support →github.com/bhaskargurram-ai ↗