-
Notifications
You must be signed in to change notification settings - Fork 0
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
uphold-gofmt, uphold-go-vet, uphold-go-build and uphold-go-test wrap the consumer toolchain, so 31 consumers run their Go gate from an uphold release instead of their own config
enhancementNew feature or requestNew feature or requestStatus: Open.#217 In HackingGate/uphold;The syntax and proof rungs stop at Rust: Go, Python, TypeScript and Bash need a grammar, an example rule and a gate recipe each
enhancementNew feature or requestNew feature or requestStatus: Open.#216 In HackingGate/uphold;Nothing states which rung of checking exists for which language: a languages by rungs matrix, native or bundled or external or not covered
documentationImprovements or additions to documentationImprovements or additions to documentationStatus: Open.#215 In HackingGate/uphold;The README first screen pitches a catalog; it should state what uphold stops, the fleet number, the install line and one policy
documentationImprovements or additions to documentationImprovements or additions to documentationStatus: Open.#214 In HackingGate/uphold;The fail-closed property is tested, not proven: extract the evaluator core and verify it with Verus
enhancementNew feature or requestNew feature or requestStatus: Open.#213 In HackingGate/uphold;A text rule sees bytes, so no bundled rule can say "no unwrap outside cfg(test)"; a rule form over the parse tree the binary already builds
enhancementNew feature or requestNew feature or requestStatus: Open.#212 In HackingGate/uphold;- Status: Open.#211 In HackingGate/uphold;
- Status: Open.#210 In HackingGate/uphold;
- Status: Open.#209 In HackingGate/uphold;