cpace

GitHub Actions workflows for this project follow the principle of least privilege. When permissions are not explicitly defined at the job level, the workflows default to the minimum required permissions (read-only where possible). The project’s CI security policy and practices are documented in docs/ci-policy.md.
https://github.com/the-sarge/cpace/blob/main/docs/ci-policy.md

Official releases are created using Git tags with unique version identifiers following semantic versioning (e.g. v0.1.0, v0.2.0). Each release is documented in CHANGELOG.md and follows the release process defined in docs/release-checklist.md.
https://github.com/the-sarge/cpace/tags
https://github.com/the-sarge/cpace/blob/main/CHANGELOG.md

Non-trivial release notes file in repository: https://github.com/the-sarge/cpace/blob/main/CHANGELOG.md. [release_notes]

The project uses Go modules as the standardized tooling for ingesting dependencies. All builds, tests, and CI pipelines use the official Go toolchain (go mod, go build, go test, etc.) via go.mod and go.sum.
https://github.com/the-sarge/cpace/blob/main/go.mod

Official releases are signed annotated Git tags, verified with git verify-tag. The project currently publishes no attached binary release assets; future release assets will be signed directly or listed in a signed hash manifest. No binary release assets are attached. Users can verify the release with git verify-tag vX.Y.Z.

The project uses Go modules for selecting, obtaining, and tracking dependencies via go.mod and go.sum. The process for reviewing and managing dependencies is documented in docs/dependency-review.md.
https://github.com/the-sarge/cpace/blob/main/docs/dependency-review.md
https://github.com/the-sarge/cpace/blob/main/go.mod

Build instructions are provided via Taskfile.yml (commands such as task quick, task check, task check:changed) and the README. The project uses the standard Go toolchain and documents validation steps. Full build documentation will be expanded as the project approaches production readiness.
https://github.com/the-sarge/cpace/blob/main/Taskfile.yml
https://github.com/the-sarge/cpace/blob/main/README.md

The project is currently maintained by a single individual (the repository owner the-sarge). This person has administrative access to all sensitive resources (repository settings, secrets, branch protection, etc.). There are no additional project members or collaborators with access to sensitive resources at this time.

The project is maintained by a single individual who serves as the primary maintainer and owner. Key responsibilities include code development and review, release management, security oversight, dependency management, responding to issues and vulnerability reports, and maintaining project documentation.

The project maintains a detailed contributor guide in CONTRIBUTING.md that outlines the contribution process, coding standards, and requirements for acceptable contributions.
https://github.com/the-sarge/cpace/blob/main/CONTRIBUTING.md

The project requires DCO signoff for contributions. GitHub web-based commit signoff is enabled, CONTRIBUTING.md documents git commit -s, the repository includes the DCO text, and pull requests are checked by a required DCO GitHub Actions status that verifies every PR commit has a Signed-off-by trailer.
https://github.com/the-sarge/cpace/blob/main/CONTRIBUTING.md
https://github.com/the-sarge/cpace/blob/main/DCO

Branch protection rules are enabled on the primary branch (main). All automated status checks from the CI pipeline (including tests and security scans) must pass before changes can be merged to the primary branch. Administrators may manually bypass checks when necessary.
https://github.com/the-sarge/cpace/settings/branches

The project’s GitHub Actions CI pipeline automatically runs the full test suite (go test ./..., vector tests, fuzz tests, and validation via Taskfile.yml) on every pull request before changes are merged to the primary branch.
https://github.com/the-sarge/cpace/blob/main/Taskfile.yml

The project maintains design and security documentation, including docs/threat-model.md and docs/security-assessment.md, which describe the system architecture, actions, actors, and security boundaries.
https://github.com/the-sarge/cpace/blob/main/docs/threat-model.md

The external interfaces of the library are documented in the README.md, which describes the public API usage (Initiator/Responder flow, Start/Respond/Finish methods, Session handling, etc.). Additional details are available in the Go source code via godoc comments.
https://github.com/the-sarge/cpace/blob/main/README.md

The project has conducted a security assessment, documented in docs/security-assessment.md, which identifies the most likely and impactful potential security problems along with associated mitigations and controls.
https://github.com/the-sarge/cpace/blob/main/docs/security-assessment.md

The project maintains a vulnerability disclosure policy in SECURITY.md. Reports are directed to private channels (email or GitHub private vulnerability reporting). The project commits to acknowledging vulnerability reports within 7 calendar days, providing initial triage/status within 14 calendar days, coordinating disclosure timing with reporters, and providing periodic updates while confirmed issues are unresolved.
https://github.com/the-sarge/cpace/blob/main/SECURITY.md

Private vulnerability reporting is available directly to the project’s security contact via email (the-sarge@the-sarge.com) and through GitHub’s private vulnerability reporting feature, as documented in SECURITY.md.
https://github.com/the-sarge/cpace/blob/main/SECURITY.md

The project commits to publicly disclosing discovered vulnerabilities through GitHub Security Advisories and updates to the CHANGELOG.md. No vulnerabilities have been publicly disclosed to date as the project remains in draft stage.
https://github.com/the-sarge/cpace/blob/main/CHANGELOG.md