Contributing

RepliMap is a commercial tool with a local-first architecture. The engine is distributed via PyPI; the replimap-community repository hosts documentation and issue tracking. The best ways to contribute are bug reports, feature requests, and telling us what your real accounts need.

Reporting Bugs

Open an issue on GitHub with:

• Description of the bug
• Steps to reproduce
• Expected vs actual behavior
• RepliMap version (replimap --version)
• Python version and OS

Include the Error Reference

When a command fails, RepliMap prints an error reference like ERR-EC2-403-A7X9 and saves a detailed local log:

# Get a summary of what happened (never a raw traceback dump)
replimap explain ERR-EC2-403-A7X9

# Full logs live locally under
ls ~/.replimap/logs/errors/

Paste the ERR- code and the explain output into your issue — it carries the exception type, the command that failed, and a reproduction command, without any of your infrastructure data.

Requesting Features & Resource Types

RepliMap scans 30+ AWS resource types today, and new types are prioritized by what real accounts need. If your account leans on a service we don't cover yet, open a feature request with:

• The AWS service / resource type
• Roughly how many of them you have
• What you'd do with them (Terraform generation, graph, coverage, audit)

We read every issue. Your feedback shapes the roadmap.

Security Issues

Questions?

• General: hello@replimap.com
• Technical Support: support@replimap.com
• Bug reports: GitHub Issues