prpm-json-best-practices

A prpm.json manifest requires top-level fields: name, version, description, format, subtype, and files array. Optional fields include repository, organization, homepage, documentation, license, dependencies, scripts, tags, keywords, and category. This structure ensures your package meets publish-ready standards.

Validate that your prpm.json includes all mandatory fields (name, version, description, format, subtype, files), correctly models packageId references and versions, and follows best-practice structuring. Validation catches errors early and ensures metadata consistency across single-package, multi-package, and collection repositories.

Yes. PRPM manifests support single-package repositories, multi-package repos with packageId references, and collections that bundle related packages. Each structure enforces the same field requirements and validation rules, with collection metadata applied at the appropriate level.

Include organization, tags, keywords, category, and documentation fields to improve discoverability. Add license, license_text, or license_url for governance. These optional fields help ensure your package is findable, properly categorized, and legally transparent.

Set eager (true/false) to control activation timing—eager packages load immediately, lazy packages load on demand. Define dependencies as an array listing required packages. Both fields ensure your package integrates correctly and declares its runtime requirements.

Standardized structuring reduces errors, improves auditability, ensures consistency across repositories, and makes manifests easier to publish and maintain. Best-practice patterns keep packages in sync and governance-compliant, especially in multi-package and collection scenarios.