developer guide
For developers
Share your PS Vita or PSP project with the community. The catalog stores your project details and CI resolves release information automatically.
Copy the platform template and save it under apps/vita/ or apps/psp/ using the next available id.
Place a matching 128x128 PNG in icons_vita/ or icons_psp/. Use the same filename as the entry slug.
Describe the project, link its GitHub repository, and let CI validate the metadata before it is published.
Entry example
{
"id": 42,
"name": "My Homebrew",
"author": "Your Name",
"category": "game",
"platform": "vita",
"titleid": "MYHB00001",
"repo": "youruser/your-repo",
"asset": "*.vpk",
"icon": "0042-my-homebrew.png",
"description": "What it does."
}Version, release date, size, download count, checksums, and download URL are filled from your latest GitHub release. Your repository's star count is published as likes. The trusted flag is recalculated from trusted_authors.json, not stars.
Automatic
Walk through one homebrew at a time: its GitHub repo, its .vpk, its icon. Add as many as you like, then download a ready-to-drop apps/vita/ + icons_vita/ package for your pull request.
Paste the GitHub repo that publishes this homebrew, or a direct link to its .vpk if it isn't hosted on GitHub.
That's not a GitHub link, so a couple of things GitHub would normally tell us are missing - fill them in:
Drop .vpk here (or any Vita vpk - it just needs to match this entry).
Drop a .vpk here, or click to choose one
Drop a 128x128 PNG icon for this entry.
Drop a .png here, or click to choose one
Don't link to copyrighted content. Only put a URL below if you have the right to redistribute that data (open assets, freeware you built yourself, etc). If players need to supply their own copy, leave the URL empty - the description above is enough.
Before opening a PR: double-check id isn't already taken by a just-merged entry, and fill in category by hand.
Added 0 entry(ies) this session:
Or open a pull request directly against robin994/NeoVitaDB-Catalog-Test - forks the repo to your account (or reuses your existing fork), commits each entry there, and opens the PR for you.
Needs a GitHub token with public_repo scope (classic, create one) or Contents + Pull requests read/write on this repo (fine-grained). Kept in memory for this page load only - never saved, never sent anywhere but api.github.com.
For catalog users
This is a static catalog. Consume the generated feeds and hosted assets from GitHub Pages; use the repository files when you need contributor metadata or want to build your own catalog.
These are the recommended endpoints for an app or website. Each item contains its resolved version, release data, download URL, checksums, and metadata.
https://robin994.github.io/NeoVitaDB-Catalog/vita.json
https://robin994.github.io/NeoVitaDB-Catalog/psp.json
Use the icon filename from a feed item. Vita icons are published at /icons/; PSP icons are published at /icons_psp/.
https://robin994.github.io/NeoVitaDB-Catalog/icons/0001-neovitadb-downloader.png
https://robin994.github.io/NeoVitaDB-Catalog/icons_psp/0001-example.png
Contributor entries and original icons are kept in the repository. These paths are useful for inspection, but generated feeds are more stable for catalog clients.
https://raw.githubusercontent.com/robin994/NeoVitaDB-Catalog/main/apps/vita/0001-neovitadb-downloader.json
https://raw.githubusercontent.com/robin994/NeoVitaDB-Catalog/main/icons_vita/0001-neovitadb-downloader.png
Replace the owner and repository name in every hosted URL after enabling GitHub Pages with the GitHub Actions source on your fork.
https://your-user.github.io/your-catalog/vita.json
https://your-user.github.io/your-catalog/icons/your-icon.png