Project
One organization, independent software projects
Secure Tools is maintained through a GitHub organization. Products and libraries retain independent repositories, release cadences, versions, implementation choices, and deployment models.
Repository model
Independent ownership
The Hub provides ecosystem definition, navigation, discovery, and high-level disclosure. It does not execute product code, load centralized plugins, discover services dynamically, or coordinate releases through a shared runtime.
No global ecosystem version
A version such as Web Utilities v2.0.0 or Secure Metadata v0.1.1 belongs to that project only. The Secure Tools ecosystem and Hub do not define a global semantic version.
Libraries remain separate
Reusable libraries can support multiple products without becoming centralized runtime dependencies. Each consuming product decides how to version, vendor, verify, and disclose its use of a library.
Status terminology
Hub-level discovery labels
Detailed alpha, beta, and release-candidate channels remain owned by each product.
- Stable
- Released for its documented use and boundaries.
- Preview
- Available for evaluation before a stable release.
- Experimental
- Exploratory work whose design may change substantially.
- In development
- Actively implemented without a current public release commitment.
- Planned
- A recognized category whose implementation is not finalized.
- Archived
- No longer actively developed; retained for reference where appropriate.
Official source