@eliware/.github 
- Features
- Requirements
- Setup
- Usage
- Development
- Testing
- Troubleshooting
- Security
- Support
- License
- Links
This repository provides reusable, organization-wide GitHub community health files and profile content for Eliware repositories. Each target repository remains responsible for project-specific requirements, implementation, and settings.
Package description: Eliware organization-wide GitHub community health files and profile. Author: Eliware eliware@eliware.org. License: MIT.
Node.js 26 and npm 12 or later are required for repository validation.
Run npm ci from the repository root to install the validation tooling.
Use the organization-wide community health content maintained here as reusable defaults for Eliware repositories. Use the release checklist issue form when tracking a release. Keep project-specific guidance in the repository that owns the project, and follow its local instructions where they apply.
Documentation: specifications
Read AGENTS.md, this README, the applicable specifications, and the authoritative documentation before changing files. Keep organization-wide defaults concise and reusable; link to the owning repository for detailed requirements and procedures.
Run npm test for aggregate validation. Use npm run lint, npm run audit, npm run format, or npm run format:check for focused stages. The scripts run through eliware-test.
Use Node.js 26 and run npm ci after dependency changes. Review the rule and file path reported by eliware-test when validation fails.
Keep credentials, secrets, decrypted data, private information, runtime output, and machine-specific state outside version control. Do not place secret values in community health files or structured records.
Use the Eliware Discord community, GitHub issues, or eliware@eliware.org. Include the relevant file path and a concise description of the issue when requesting help.
Documentation: specifications