vfhe

The repository's default workflow token permission is read-only, and every workflow additionally declares an explicit least-privilege permissions: block, widened only per job where required (e.g. id-token: write solely in publish jobs).

Every release carries a unique SemVer identifier: an immutable git tag, an immutable PyPI version (PyPI forbids reuse), and the package version derived from the tag by setuptools-scm.

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

Dependencies are ingested exclusively through standard ecosystem tooling: pip/setuptools resolving pyproject.toml declarations in an isolated build, and pinned git submodules for vendored native sources.

Every release asset is accounted for cryptographically: SLSA build provenance (Sigstore-signed, containing the sdist's digest) is generated at build time and attached to the GitHub release, and PyPI publication carries PEP 740 attestations via Trusted Publishing.

docs/DEVELOPMENT.md ("Dependencies") documents selection policy (minimal runtime surface, floor semantics), acquisition (PyPI via pyproject.toml; vendored submodules pinned to commits with provenance in NOTICE), and tracking (weekly Dependabot across actions/pip/docker, dependency review on PRs, per-release SBOM).

docs/DEVELOPMENT.md documents prerequisites (Python, pip, C compiler, submodules) and the full build (make deps / make build), with CONTRIBUTING.md covering contributor setup; builds are automated via Makefile targets.

AUTHORS.md lists the maintainers holding access to sensitive resources (GitHub organization, PyPI project, release pipeline) with their GitHub identities, alongside the full author list.

AUTHORS.md describes the roles: maintainers review and merge, cut releases, and handle security reports; authors contribute research and code through the same review process as external contributors.

CONTRIBUTING.md defines acceptance requirements: coding standards (ruff, clang-format, pyright, enforced by hooks and CI), testing requirements, the pre-PR checklist, commit conventions, and the discuss-large-changes-first rule; CI OK is the single required check embodying them.

Contributions are made on GitHub, whose Terms of Service (section D.6, inbound=outbound) require every contributor to have the right to license their contribution under the repository license; the project deliberately relies on this plus Apache-2.0 p.5, as the criterion's own text allows.

The default-branch ruleset requires the CI OK status check to pass before merge; no optional checks are configured as required.

Every pull request runs lint, C unit tests, the complete Python suite across Linux/macOS and Python 3.10-3.14, an sdist install-and-smoke check, and fuzzing of changed code, all gating merge via CI OK; results are public, and contributors run the same suites locally via make test.

docs/DEVELOPMENT.md documents the system's design and actors: the module architecture, the Python/C native boundary (wrappers > cffi > single LTO'd engine), the build pipeline, and the CI/release actors; per-module READMEs describe each subsystem.

The external interface is the documented Python API: module surfaces listed in the README, usage documented in docs/USAGE.md, and each module's public API defined by its init exports with docstrings. The C layer is internal (reached only through the packaged cffi binding), not an external interface.

SECURITY.md's scope section records the project's security assessment: the most impactful problem classes (cryptographic errors, memory safety in the C kernels, key/plaintext recovery) and explicitly acknowledged gaps (unaudited status, timing side channels not hardened). Continuous adversarial testing backs it: libFuzzer with ASan/UBSan per PR and nightly, CodeQL, and sanitizer-enabled test runs.

SECURITY.md defines coordinated vulnerability disclosure: private reporting channels, acknowledgment within 7 days, coordinated disclosure with a 90-day window, and advisory publication upon fix.

SECURITY.md provides two private channels directly to the security contacts: GitHub private vulnerability reporting (preferred) and maintainers@vfhe.ai.

SECURITY.md commits to publishing fixed vulnerabilities as GitHub security advisories naming affected versions and remediation; the changelog additionally records security fixes per release.