AA Alt Corp
aa-altcorp is an Alliance Auth plugin for tracking alt-corporation relationships and auditing whether member-related characters, corporations, and alliances have the expected contact standings and access-list permissions.
It reads Alliance Auth and aa-contacts data, compares that data with configured policy, and reports differences for human review. It does not modify EVE contacts or access lists.
What it does
- Records corporations and characters associated with Alliance Auth users.
- Audits contact standings and access-list access for valid members.
- Detects blue contacts and ACL entries without a matching Auth relationship.
- Supports policies for Auth states, groups, positive contacts, named entities, and individual access lists.
- Creates separate alert facets for contact and ACL problems.
- Supports temporary exemptions with expiry, revocation, and an audit trail.
- Delivers alerts through
allianceauth-discordbotor a plain webhook. - Keeps the older corporation review flow available for existing installations.
The alert engine is informational. It never writes to EVE contacts or EVE access lists; changes remain manual administrator actions.
Requirements
The plugin supports Python 3.10 through 3.13 and requires:
Alliance Auth >= 5.3, < 6
aa-contacts >= 1.0.1, < 2
django-esi >= 10.0.0, < 11
croniter >= 6, < 7
django-celery-beat >= 2.7, < 3
Installation
Activate the virtual environment used by Alliance Auth and install the package:
pip install allianceauth-altcorp
Add the application to INSTALLED_APPS:
INSTALLED_APPS = [
# ...
"aa_altcorp",
]
Run migrations and collect static files:
python manage.py migrate
python manage.py collectstatic --noinput
The app configuration is aa_altcorp.apps.AaAltcorpConfig.
Configuration
Open Django Admin → Alt Corp settings after installation. Configure the standing target, valid Auth states, expected entity scope, alert delivery, notification interval, and Discord details there.
Alerting defaults to disabled so an upgrade does not immediately send notifications. Configure the expected state and policies first, then enable alerts.
An access list produces a missing-access alert only when it has an Access list policy in Django Admin. Present-but-unjustified entries can still produce alerts without a policy.
Scheduling
Create the periodic audit, alert scan, and Discord refresh tasks with:
python manage.py schedule_altcorp_tasks --scan-cron "0 * * * *"
The command is idempotent. --hours changes the audit interval, and --remove removes the tasks it created. On larger installations, schedule aa_altcorp.tasks.sync_all_access_lists separately to fan ACL synchronization out across characters.
Discord alerts
Discord integration is provided by allianceauth-discordbot. Go to that repository for installation, configuration, and bot worker instructions.
Permissions
| Permission | Purpose |
|---|---|
aa_altcorp.basic_access |
View plugin pages |
aa_altcorp.manage_relationships |
Attach corporations and characters |
aa_altcorp.view_alerts |
Reserved for future use |
aa_altcorp.manage_alerts |
Reserved for future use |
Alerts, exemptions, and access-list policies are managed through Django Admin permissions. The reserved alert permissions do not independently grant admin access. Discord authorization follows the configured roles.
Development
python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e '.[dev]'
pre-commit run --all-files
pytest
tox -e py312
On Windows, run the complete local pipeline with:
.\scripts\run_pipeline.ps1
GitHub Actions runs pre-commit, the Auth-absent pytest suite on Python 3.10–3.13, and the Alliance Auth integration suite on Python 3.12. See RELEASING.md for the first push, development workflow, and releases.
License
This project is licensed under the GNU General Public License v3.0. See LICENSE.
Metadata
Release files for allianceauth-altcorp 0.0.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| allianceauth_altcorp-0.0.14.tar.gz | 128.4 kB | Without provenance | Details for allianceauth_altcorp-0.0.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| allianceauth_altcorp-0.0.14-py3-none-any.whl | Python 3 | none | any | Details for allianceauth_altcorp-0.0.14-py3-none-any.whl |
Total release size: 245.7 kB
Release files / allianceauth_altcorp-0.0.14.tar.gz
| Download URL | allianceauth_altcorp-0.0.14.tar.gz |
|---|---|
| Size | 128.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dd0349a316e9a79bd72389d0c731ad8b907fce96024cae496005c1eb7baf98a
|
|
BLAKE2b-256 checksum How to use checksums |
7390b6a338f8c44fb3d995415e5e21e0f30c450e664f1873136560978c0e384d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.0
|
Release files / allianceauth_altcorp-0.0.14-py3-none-any.whl
| Download URL | allianceauth_altcorp-0.0.14-py3-none-any.whl |
|---|---|
| Size | 117.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbb59cb7690903f6bf980281fb4dd9216549cc0c480c072600ba148de1221b44
|
|
BLAKE2b-256 checksum How to use checksums |
4b182ae65664d3f8b162376509f7c01d6b9fc1e69ba432dc1bc3e8964aad04ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.0
|
Security for allianceauth-altcorp 0.0.14
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.