github-automated-repos is an MIT-licensed TypeScript and ReactJS library, published on npm, that builds the project list on a portfolio or website from GitHub repository Topics instead of hand-edited code files, and it is aimed at frontend developers who publish a personal project page.
What it is
github-automated-repos is a ReactJS library plus a companion CLI, written in TypeScript and released under the MIT licence. It is listed in this registry under Business Software / Project & Work Management, carries the npm package name github-automated-repos and the CLI name github-automated-repos-cli, and is registered as a GitHub API and GitHub automation tool. The project has 1686 stars, 24 forks, 0 open issues, and its most recent push is dated 2026-01-01. Its homepage is a stack icon reference at https://github-automated-repos.vercel.app/stackicons.
The concrete problem it solves is stated directly in the README. A portfolio or website normally tracks its projects either in project.js files that force the author to edit code every time a project changes, or through raw GitHub API calls that offer no data control. This library replaces both paths. Configuration is written once in the application through the useGitHubAutomatedRepos hook with a GitHub username and a keyword, and from then on the set of visible projects is managed on GitHub itself, in the Topics field of each repository. A keyword such as attached, portfolio or featured decides which repositories appear, and each project card can carry a representative icon and the stacks used.
Key capabilities
useGitHubAutomatedRepos hook configured with GitHubUsername and KeyWord as the single in-code configuration point.npx github-automated-repos-cli init scaffolding command that prompts for the GitHub username and fetches public repositories directly from GitHub.- Repository filtering by keyword placed in the GitHub Topics field, with
attached, portfolio and featured given as working examples.
- Template file generation, with terminal output showing a written target such as
app\projects\page.tsx.
- Interactive overwrite prompt when the target file already exists, so the page can be regenerated.
- Card customisation through a representative icon and the list of stacks used, supported by the icon reference at
/stackicons.
- Published as the npm package
github-automated-repos, with a CodeFactor code quality badge in the README.
Who uses it and how
- Frontend developers and developers building a portfolio site, matching the
developer-portfolio, frontend-developers and github-portfolio topics.
- Next.js App Router projects: the CLI writes into a path such as
app/projects/page.tsx and reports the page ready at http://localhost:3000/projects.
- Maintainers with many repositories who want to add or remove a project from the site by editing a repository topic rather than shipping a code change.
- Authors who want each project card to show a chosen icon and the stacks used, using the homepage icon reference as the source.
- Adoption is modest but real: 1686 stars and 24 forks on the repository.
Getting started
Run npx github-automated-repos-cli init and answer the two prompts for GitHub username and filter keyword, or install the github-automated-repos npm package and configure the useGitHubAutomatedRepos hook directly.
How it compares
No paid products and no comparable tools are named in the facts for this entry, so the only interface it is contrasted against is the GitHub API itself, which the README describes as offering no data control. It stands alone in this registry on that basis.
When to use it — and when not to
Use it when the project page already lives in a React or Next.js application and the desired source of truth is GitHub Topics, since there is no database, storage layer or SMTP service to operate and the data is read from GitHub. The README is sparse and partly written in Portuguese with leftover raw image markup and comment fragments, so expect to read the CLI prompts and terminal output rather than the prose. Do not pick it for a non-React stack, or when project data must come from a source other than public GitHub repositories.
project readme (upstream, from github) — read inline
✅ github-automated-repos is the library,ReactJS, that gives you the power to control your GitHub data, your projects on the portfolio / website,
in your own GitHub in one place!
❌ project.js files ( edit code )
❌ GitHub API ( no data control )
https://github-automated-repos.vercel.app
Contributing Guidelines
About Library
This library automates the view your GitHub projects on your porfolio / website in one place. But how? Make the code configuration only once in your application with github-automated-repos, and manage the view of your projects on GitHub in the Topics field. Choose which project will be seen, and you can even customize your project card, for example, with a representative icon and show which stacks were used. All in one place!
Details
init - CLI
1. Run Command
npx github-automated-repos-cli init
2. Enter data
🦑 GitHub Username
You will be prompted to enter your GitHub username.
This is used to fetch your public repositories directly from GitHub.
✔ GitHub username: xxxxxx
🔑 Keyword (Repository Filter)
Next, you’ll choose a keyword (for example: attached , portfolio , featured ).
This keyword will be used to filter repositories via the GitHub Topics field.
✔ Keyword to filter (e.g. 'attached'): attached
[!IMPORTANT]
Don't forget to enter your Keyword in the Topics field of each project so it appears on the generated page.
3. Terminal Result
√ Target file already exists
