← Browse

@apache/steve

A

Apache Steve is software to conduct a vote using the STV (Single Transferable Vote) and other voting algorithms.

instructionscodex

Install

agr install @apache/steve --target codex

Writes 1 file into AGENTS.md, pinned to git-18287034.

  • AGENTS.md

Document

Coding Agent Context

This project uses uv for dependency management and enforces strict linting, formatting, and type-checking standards. All Coding Agents MUST follow these instructions after generating or modifying code to ensure compatibility with the project's CI/CD pipelines.

Post-Generation Checklist

From the repository root (where this AGENTS.md file lives), run the following commands inside the v3/ directory:

  1. Code Formatting: Format the code using ruff.

    uv run ruff format .
    
  2. Linting: Run ruff check to identify and fix potential issues.

    uv run ruff check --fix .
    
  3. Type Checking: Verify type safety with mypy.

    uv run mypy --ignore-missing-imports .
    

Development Standards

  • Language: All code, documentation, and comments MUST be written in English.
  • Dependencies: Use uv for all dependency management tasks (e.g., uv sync, uv run).
  • CI Alignment: These steps align with the .github/workflows/linting.yml and .github/workflows/type-tests.yml configurations.

Ensure all checks pass before considering a task complete.

Repository README

Describes apache/steve as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Welcome to Apache Steve http://steve.apache.org/

Apache Steve is software to conduct a vote using the STV (Single Transferable Vote) and other voting algorithms. The tool grew out of the voting system used to elect the Apache Software Foundation Board of Directors.

Read more about STV at http://en.wikipedia.org/wiki/Single_transferable_vote

[!NOTE]

The v3 directory contains the current (ongoing) version of Steve. Read the v3/README.md file for more information about this version. Read the Getting Started Guide to set up a development environment for v3.

Getting Started

Getting Started documentation can be found at: http://steve.apache.org/demo.html Otherwise, come to the #steve channel on the Slack workspace at the-asf.slack.com, and we'd be glad to help you.

Documentation

Documentation may be found at http://steve.apache.org/documentation.html

Contributions to the documentation are very welcome.

Mailing Lists

Discussion about Steve takes place on the following mailing lists:

dev@steve.apache.org    - About using Steve and developing Steve

Notification on all code changes are sent to the following mailing list:

commits@steve.apache.org

The mailing lists are open to anyone and publicly archived.

You can subscribe the mailing lists by sending a message to <LIST>-subscribe@steve.apache.org (for example dev-subscribe@steve.apache.org). To unsubscribe, send a message to <LIST>-unsubscribe@steve.apache.org. For more instructions, send a message to <LIST>-help@steve.apache.org.

Issue Tracker

If you encounter errors in Steve or want to suggest an improvement or a new feature, please visit the Steve issue tracker at https://github.com/apache/steve/issues

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-18287034ab7d2026-08-06