Open Issues Need Help
View All on GitHub Naming for plugins/scheme implementations. 21 minutes ago
AI Summary: The Veraison project currently uses inconsistent, ad-hoc naming for its plugins and scheme implementations, which is problematic as these names form part of its public interface. This issue proposes devising and documenting a consistent naming scheme to prevent collisions (e.g., using vendor prefixes) and ensure clarity (e.g., consistent use of suffixes for technology). The existing codebase will also need to be refactored to comply with the new scheme.
Complexity:
4/5
enhancement good first issue
BUG: the `.github/workflows/ci-go-cover.yml` action relies on an action that is x86_64-specific about 2 hours ago
bug good first issue
Re-evaluate test coverage about 2 hours ago
good first issue
Make Endorsement Store Interface Key names consistent about 2 hours ago
bug good first issue
feature: use gh "Artifact Attestations" about 2 hours ago
enhancement good first issue
Dependency on `machine-id` about 2 hours ago
bug good first issue
Versioning for plugins/scheme implementations. about 2 hours ago
enhancement good first issue
BUG: REST API should not embed versioning in the URL about 2 hours ago
bug good first issue
Parsec TPM endorsements - consider extending with vendor and model info about 2 hours ago
good first issue
Improve unit test coverage of services repository about 2 hours ago
enhancement good first issue
Add X.509 cert chain to TrustAnchor types about 2 hours ago
enhancement good first issue
BUG: Session nonce from /challenge-response/v1//newSession should be a URL-safe base64 string about 3 hours ago
bug good first issue
Broken link in debian deployment README about 3 hours ago
documentation good first issue