The official package registry for the Razy
framework. Clients (php Razy.phar search|install|sync|pkg) resolve modules from
this repository with zero configuration — it is the built-in default registry
(Razy\RepositoryManager::DEFAULT_OFFICIAL_*).
| What | Where | Pinned by |
|---|---|---|
| Index | index.json at the root of the main branch |
RepositoryManager::buildRawUrl() → raw.githubusercontent.com/{owner}/{repo}/{branch}/index.json |
| Manifest | {module}/manifest.json (module-code directory) |
RepositoryManager::getManifest() |
| Release asset | GitHub Release with tag {vendor}-{module}-v{version} and asset filename {version}.phar |
RepositoryManager::buildReleaseAssetUrl() |
Example: module dashboard version 1.0.0 → tag dashboard-v1.0.0, asset
1.0.0.phar, downloadable at
https://github.com/RayFungHK/Razy-Repository/releases/download/dashboard-v1.0.0/1.0.0.phar.
Top-level object keyed by module code (vendor/module or bare name).
Each entry:
{
"description": "one-line summary",
"author": "Name <email>",
"type": "module | package",
"latest": "1.0.0",
"versions": ["1.0.0"],
"releases": {
"1.0.0": { "sha256": "<hex digest of the .phar>" }
}
}- An entry that claims a checksum (
releases.<v>.sha256, or the legacy flatsha256key) makes verification mandatory: install/sync/pkg download the artifact, hash it, and abort before extracting on any mismatch. - A claimed-but-empty digest aborts too (
PackageVerifiertreats it as a broken promise, not an absence of one). - v1 entries with no checksum keys install with a loud
CANNOT BE VERIFIEDwarning — publish digests, don't rely on the warning path. - Compute the digest of the exact
.pharyou upload:sha256sum 1.0.0.phar(orGet-FileHash 1.0.0.phar -Algorithm SHA256).
- Build the module's
.phar(php Razy.phar package <module>). gh release create {vendor}-{module}-v{version} path/to/{version}.phar --repo RayFungHK/Razy-Repository(the filename must already be{version}.phar).- Add/extend the entry in
index.json(versions[],latest,releases.{version}.sha256) and, for a new module, its{module}/manifest.json. - Commit to
main— clients pick the index up immediately (raw caching is a few minutes at most).
Integrity and transport rules are enforced client-side by
Razy\PackageVerifier + Razy\ArchiveSafety (HTTPS-only downloads; zip-slip
validated extraction). Index signing is planned (dossier S2); until then
the HTTPS+checksum chain is the strongest available claim.