Skip to content
BranchesTags

Repository files navigation

EnvsBot - Modular XMPP Bot Framework - Build Status

EnvsBot is a modular XMPP bot for rooms and direct chats, built with Python and slixmpp. It provides a plugin-based command framework, room-specific feature toggles, user/role management, SQLite persistence, generated command documentation, vCard/avatar publishing, and a growing set of utility, community and fun plugins.

This repository is the envs.net maintained fork of the XMPPBot project at redterminal-org/XMPPBot. It is developed independently from Dan's original bot and tailored for the envs.net XMPP/pubnix setup, while remaining useful for other small XMPP communities.

The bot was originally developed for the envs pubnix/tilde community and follows the spirit of classic tilde bots: useful, extensible, friendly in shared rooms, and easy to run on a small server.

Features

  • Modular plugin architecture with dynamic load, unload and reload support
  • Decorator-based command registry with roles, aliases, usage metadata and generated help
  • Practical tutorial in docs/tutorial.md, generated command overview in docs/commands.md, plugin guides in docs/plugins/, runtime help guide in docs/help.md, diagnostics guide in docs/diagnostics.md, and architecture overview in docs/architecture.md
  • XMPP MUC and direct-message command handling
  • Room management with persistent autojoin rooms and per-room plugin toggles
  • User registration, hardened role management, last-seen tracking and nickname lookup
  • Safe runtime config inspection, validation and reload commands
  • Built-in version command and optional GitHub release update checks
  • SQLite-backed persistence with doctor checks, audit log, managed ZIP backups and documented offline maintenance
  • vCard and avatar support via XEP-0054, XEP-0084 and XEP-0153
  • RSS/Atom feed watcher for room announcements
  • URL metadata checks for links, files and YouTube videos
  • Shared persistent recent-message cache for reply-aware plugins
  • Weather, translation, vCard lookup, XMPP diagnostics, reminders, polls, pins, tell messages and utility commands
  • Community/fun plugins such as IdleRPG, ducks, dice, karma, sed corrections and XKCD
  • Pytest-based test suite with Drone CI and GitHub Actions support

Mirrors

  • https://git.envs.net/envs/envsbot
  • https://github.com/envs-net/envsbot

Installation / Quickstart

Optional interactive deployment helper

For production installs and updates, ./scripts/deploy.sh can orchestrate the same safety checks shown in the manual examples below. A bare invocation only prints help and performs no action:

./scripts/deploy.sh
./scripts/deploy.sh status
./scripts/deploy.sh check
./scripts/deploy.sh install --dry-run
./scripts/deploy.sh update --dry-run

install/update require explicit confirmation, and stopping/starting systemd are confirmed separately. Existing config, database, vCard, operator-managed avatar and systemd unit files are preserved; an existing service file is never replaced. Automatic updates select stable vX.Y.Z release tags only: they never deploy main and never downgrade to an older tag. An intentional rollback requires an explicit --to TAG --allow-downgrade and does not downgrade the database schema. Release discovery queries the configured Git remote without importing every remote tag; only the selected release tag is fetched, so an unrelated conflicting local historical tag cannot break the update. Set ENVSBOT_DEPLOY_REMOTE when the release remote cannot be inferred safely. Use --root, --venv, --config, --service, --user, --group and --unit for non-standard layouts. See docs/deployment.md for the complete safety model and supported environment overrides.

The command-by-command installation/update instructions below remain fully supported.

Requires Python 3.12+.

For production installations, use the latest tagged release instead of the main branch. The main branch is the active development branch and may contain changes that are not part of a stable release yet.

The quickstart below queries the remote and checks out the newest stable vX.Y.Z tag. You can also replace LATEST_TAG with an explicit release such as vX.Y.Z.

sudo useradd --system --home /srv/envsbot --shell /usr/sbin/nologin envsbot
sudo install -d -o envsbot -g envsbot -m 0750 /srv/envsbot
sudo -u envsbot -H bash

# Run the remaining commands in this envsbot shell.
cd /srv/envsbot
git clone --no-tags https://git.envs.net/envs/envsbot.git .
REMOTE=origin
LATEST_TAG="$(
  git ls-remote --tags --refs --sort=-version:refname "$REMOTE" |
  awk '{sub("^refs/tags/", "", $2); print $2}' |
  grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' |
  head -n1
)"
test -n "$LATEST_TAG"
git fetch --no-tags "$REMOTE" "refs/tags/$LATEST_TAG:refs/tags/$LATEST_TAG"
git checkout "$LATEST_TAG"
echo "Using EnvsBot release $LATEST_TAG"

PYTHON_MINOR="$(python3 -c 'import sys; print(f"{sys.version_info.major}{sys.version_info.minor}")')"
CONSTRAINTS="constraints/python${PYTHON_MINOR}.txt"
test -f "$CONSTRAINTS"

python3 -m venv .venv
source .venv/bin/activate
pip install -c "$CONSTRAINTS" -e .

if [ ! -e config.py ]; then
  install -m 0600 config_sample.py config.py
else
  echo "KEEP existing config.py"
fi
$EDITOR config.py

if [ ! -e vcard.py ]; then
  install -m 0600 vcard_sample.py vcard.py
else
  echo "KEEP existing vcard.py"
fi
$EDITOR vcard.py

envsbot --check
envsbot

Updating

Use tagged releases for updates as well. Do not update a production bot by blindly pulling main.

Example update flow for a systemd installation. Stop the running bot before changing the checkout, dependencies or schema, and deploy a tagged release rather than a moving main checkout:

sudo systemctl stop envsbot.service

cd /srv/envsbot
REMOTE=origin
sudo -u envsbot git fetch --prune --no-tags "$REMOTE"
LATEST_TAG="$(
  sudo -u envsbot git ls-remote --tags --refs --sort=-version:refname "$REMOTE" |
  awk '{sub("^refs/tags/", "", $2); print $2}' |
  grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' |
  head -n1
)"
test -n "$LATEST_TAG"
sudo -u envsbot git fetch --no-tags "$REMOTE" "refs/tags/$LATEST_TAG:refs/tags/$LATEST_TAG"
sudo -u envsbot git checkout "$LATEST_TAG"
echo "Using EnvsBot release $LATEST_TAG"

PYTHON_MINOR="$(sudo -u envsbot .venv/bin/python -c 'import sys; print(f"{sys.version_info.major}{sys.version_info.minor}")')"
CONSTRAINTS="constraints/python${PYTHON_MINOR}.txt"
test -f "$CONSTRAINTS"
sudo -u envsbot .venv/bin/pip install -c "$CONSTRAINTS" -e .
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot db status
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot db migrate --dry-run
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot db backup
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot db migrate
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot db schema
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot db check
sudo -u envsbot env ENVSBOT_CONFIG=/etc/envsbot/config.py .venv/bin/envsbot --check

sudo systemctl start envsbot.service
sudo journalctl -u envsbot.service -f

Before updating, keep a copy of the active config, the configured DB_FILE and mutable support files such as vcard.py, chat_slang.csv and the slang review queues, or create a managed bot backup with ,backup. Hardened installations normally keep these below /etc/envsbot and RUNTIME_DATA_DIR rather than inside the application checkout. After updating, check config_sample.py for new options and compare your live config with ,config diff.

Minimal Configuration

Create an owner-only runtime config and set at least:

install -m 600 config_sample.py config.py

Then edit config.py:

JID = "envsbot@example.org"
PASSWORD = "secret"
NICK = "EnvsBot"
RESOURCE = "service"  # optional; set None to let server choose
OWNER = "admin@example.org"

COMMAND_PREFIX = ","
TIMEZONE = "Europe/Berlin"
DB_FILE = "data/bot.db"
STOP_CMD = []
STOP_CMD_TIMEOUT_SECONDS = 10

AVATAR_PATH = "avatar.jpg"  # bundled default; use data/avatar.jpg for a custom file
AVATAR_TYPE = "image/jpeg"

Optional CONNECT_HOST, CONNECT_PORT and CONNECT_DIRECT_TLS values can be used when the XMPP server address differs from the JID domain, default client port or STARTTLS mode. For direct TLS, set:

CONNECT_DIRECT_TLS = True
CONNECT_PORT = 5223

config_sample.py also contains operator tuning sections for network timeouts, default pagination, URL checks, RSS backoff and per-poll burst limits, birthday scans, sed/poll/pin limits, anti-spam delays and XKCD indexing. These values are safe to adjust without editing plugin code.

DEFAULT_PAGINATION = "all" makes paginated commands show all entries by default. Set it to a positive integer, for example 20, to show page 1 with that many entries unless the user explicitly passes all, last or a page number.

Runtime-safe configuration checks are available through:

,config show
,config diff
,config search rss
,config set LOG_LEVEL DEBUG
,config unset LOG_LEVEL
,config validate
,config reload

Secrets such as passwords and API keys are redacted in bot output. ,config set rejects startup-only, secret and protected options.

Optional release update checks can be enabled with:

VERSION_CHECK_ENABLED = True
VERSION_CHECK_INTERVAL = 3600
VERSION_CHECK_URL = "https://github.com/envs-net/envsbot/releases/latest"
VERSION_CHECK_NOTIFY_JID = "admin@example.org"

When VERSION_CHECK_NOTIFY_JID is empty, automatic update notifications are sent to the configured owner JID. If VERSION_CHECK_NOTIFY_JID is a MUC room JID, EnvsBot joins that room before sending the notification and uses a groupchat message. After a fully healthy startup, EnvsBot also records the running version in RUNTIME_DATA_DIR. When a later healthy startup detects a version change, it sends ⬆️ EnvsBot updated successfully: vOLD → vNEW to the same VERSION_CHECK_NOTIFY_JID target (or OWNER). The first startup only seeds this state, normal restarts on the same version stay silent, and degraded startups with plugin load failures do not advance the recorded version. Failed deliveries remain pending and are retried after a later healthy process start. The notification room is joined at send time and is not automatically added to the stored room list unless you also add it with ,rooms add or ,rooms join. Manual checks through ,checkupdate work even when the periodic worker is disabled.

Incoming MUC invites can be reviewed before the bot joins the invited room:

ROOM_INVITES_ENABLED = True
ROOM_INVITE_NOTIFY_JID = ""  # empty = VERSION_CHECK_NOTIFY_JID, then OWNER
ROOM_INVITE_MAX_AGE_DAYS = 30

When invited to a room, EnvsBot stores a pending invite and notifies ROOM_INVITE_NOTIFY_JID, VERSION_CHECK_NOTIFY_JID, or the configured owner. If the notification target is a MUC room, the bot joins it before sending the approval message. The bot does not join the invited room until an admin accepts the invite with ,rooms invite accept <id>. Declined invites are removed with ,rooms invite decline <id>.

For migration, legacy config.json is still accepted when no config.py exists, but new installations should use the Python config file. The JSON sample is no longer maintained.

vCard and Avatar

Copy vcard_sample.py to vcard.py and adjust the bot profile. EnvsBot can publish profile data and an avatar through XMPP vCard/PEP mechanisms.

Avatar-related config keys:

AVATAR_PATH = "avatar.jpg"  # bundled default
AVATAR_TYPE = "image/jpeg"

The default avatar is packaged with envsbot; no avatar.jpg needs to be copied into the repository root. Set AVATAR_PATH = "data/avatar.jpg" (or another path) to publish a custom avatar, or AVATAR_PATH = None to disable avatar publishing.

Supported avatar MIME types are usually image/jpeg and image/png. The bot publishes the avatar hash in presence so MUC occupants can discover the avatar even if they do not have the bot in their roster.

Important Commands

Examples assume the default command prefix ,.

Command Description
,help Show available help topics and commands
,help all Show the full visible help output
,help <plugin> Show focused help for one plugin
,help ,<command> Show focused help for one command
,bot status [full] / ,status [full] Show compact bot/runtime/XMPP/database health; full adds room, plugin, task and cache diagnostics
,tasks [full] [plugin <name>] [status] Show supervised background task status
,bot version / ,version Show the running bot version and latest checked release
,bot checkupdate / ,checkupdate / ,updatecheck Check GitHub releases for a newer version
,config show [all/page/last] Show redacted runtime configuration
,config diff [all/page/last] Show values that differ from config_sample.py defaults
,config search/find <query> Search visible config keys and values
,config set <KEY> <value> Persist and apply one runtime-writable config value
,config unset <KEY> Reset one runtime-writable config value to the sample default
,config validate Validate config.py
,config reload Reload runtime-safe configuration
,backup / ,backup create [reason] Create a managed ZIP backup
,backup list [all/page/last] List managed backup archives
,backup show <archive|last> Show backup manifest details
,restore <archive|last> confirm Restore a managed backup after explicit confirmation
,audit last [limit] Show recent administrative audit events
,audit user <jid> Show audit events for one actor
,plugins list [all/page/last] List core and optional plugins
,plugins load <name> Load a plugin at runtime
,plugins unload <name> Unload an optional plugin at runtime
,plugins reload <name> Reload a plugin at runtime
,rooms list [all/page/last] List known rooms
,rooms add <room_jid> <nick> [autojoin] Add a room to the database
,rooms join <room_jid> [nick] Join a room immediately
,rooms invite list [all/page/last] List pending room invites
,rooms invite accept/decline <id> Accept or decline a pending room invite
,rooms leave <room_jid> Leave a room
,rooms plugins [<room_jid>] [all/page/last] Show plugin states for a room
,rooms enable [<room_jid>] <plugin> Enable a room-toggleable plugin for a room
,rooms disable [<room_jid>] <plugin> Disable a room-toggleable plugin for a room
,users roles Show available user roles
,users admins [all/page/last] List privileged users
,users info [jid|nick] Show your own user record; admins may inspect another user
,users role <jid> <role> Create a user record if needed and assign or change its role
,users grant <jid> <plugin> [plugin ...] Grant room-scoped plugin permissions, for example rss pin poll
,users revoke <jid> <plugin> [plugin ...] Revoke room-scoped plugin permissions
,users grants <jid> Show room-scoped plugin permissions

Room plugin settings can be changed in multiple contexts. In a MUC PM or directly in the room, the bot infers the room automatically. In a normal private chat or operational notification room, pass the target room explicitly, for example ,rooms disable room@conference.example.org xkcd. The sender must be a room admin/owner in the target room or have a bot moderator/admin role. Selected plugins can also be delegated per user with ,users grant <jid> rss pin poll; these grants are room-scoped and still require the user to be owner/admin in the target room. The global defaults used for new rooms and ,rooms set_plugin_defaults are configured with ROOM_PLUGIN_DEFAULTS in config.py; per-room changes remain stored in the database.

EnvsBot has no separate fixed ADMIN_ROOM setting. Global bot privileges are controlled by OWNER, ADMINS and stored bot roles. Update and invite notification targets are configured separately with VERSION_CHECK_NOTIFY_JID and ROOM_INVITE_NOTIFY_JID.

For paginated commands, all disables paging and prints the full result set. New operators should start with docs/tutorial.md; full reference: docs/commands.md. ,help <command> without the command prefix remains accepted as a convenience shortcut when it is not ambiguous with a plugin name.

Plugins

EnvsBot now separates built-in bot functionality from optional room/community features:

  • core_plugins/ contains bot/admin building blocks. These plugins keep their public names such as help, rooms, users and backups, but they are protected from runtime unloads. Reloading them is still supported.
  • plugins/ contains optional room, utility and community features that can be loaded, unloaded and reloaded at runtime.

Core plugins:

  • _admin - restart, shutdown and runtime status/statistics
  • _core - shared helpers for plugins
  • _reg_profile - startup profile, vCard and avatar publishing
  • help - dynamic command and plugin help
  • plugins - runtime plugin management
  • tasks - background task inspection
  • rooms - room persistence, joining and per-room feature toggles
  • users - user registration, roles, admin listings and last-seen tracking
  • config_cmd - safe config inspection, validation and reload
  • backups - managed ZIP backups and restore commands
  • audit - admin audit log viewer
  • presence - bot presence/status controls

Optional plugins:

  • birthday_notify - birthday announcements for opted-in rooms
  • dice - dice rolling with common notation
  • ducks - duck game with persistent stats
  • info - Wikipedia, Fediverse, Urban Dictionary and acronym helpers
  • karma - room-local karma tracking
  • pin - save and manage pinned messages
  • poll - room polls with voting and history
  • reminder - timed reminders with relative, absolute and timezone-aware scheduling
  • rss - RSS/Atom feed watcher with stable feed numbers, delete-by-number and optional per-room/per-feed output templates
  • sed - sed-style message corrections
  • tell - offline messages delivered when users rejoin
  • tools - ping, echo, time/date, seen and timestamp helpers
  • translate - translate text or replied-to room messages with auto-detection
  • urlcheck - URL title, metadata, file and YouTube lookup
  • vcard - public vCard lookup helpers
  • weather - weather lookup from configured location data or city/ZIP input
  • xkcd - latest, random, specific and searched XKCD comics
  • xmpp - XMPP diagnostics, discovery, uptime, version and SRV checks

Reminder timezone notes: absolute reminders accept optional timezone tokens such as CEST, CET, UTC, Europe/Berlin or +02:00. Without an explicit token, the bot uses the user profile timezone from ,timezone set <IANA timezone>, then REMINDER_DEFAULT_TIMEZONE from config.py, then UTC.

Systemd Service

For hardened production installs, keep application code read-only and separate runtime-writable files from /srv/envsbot:

/srv/envsbot/              application + virtualenv (read-only to the service)
/etc/envsbot/config.py     runtime-editable configuration
/var/lib/envsbot/          SQLite DB, backups, exports and runtime state
/var/log/envsbot/          rotating file logs

The canonical production unit is generated from the active installation with envsbot systemd render. It uses ProtectSystem=strict and grants writes only to the configured runtime paths. Set ENVSBOT_CONFIG=/etc/envsbot/config.py and configure LOG_DIR=/var/log/envsbot, and configure DB_FILE, RUNTIME_DATA_DIR, BACKUP_DIR, RESTART_NOTIFICATION_FILE and the IdleRPG export_path below /var/lib/envsbot. RUNTIME_DATA_DIR holds writable support files such as vcard.py, chat_slang.csv, slang review queues, profile hash markers and envsbot_version_state.json. Runtime config.py and vcard.py are read without writing adjacent Python bytecode caches. Logging is written both to the configured rotating file and stderr; under systemd the stderr copy is available through journalctl (and may also reach syslog when the host forwards journal records).

Use the deployment helper before installing or replacing the unit. Select the same external config path that the service should keep using:

export ENVSBOT_CONFIG=/etc/envsbot/config.py
envsbot systemd check
envsbot systemd render > /tmp/envsbot.service.new
if sudo test -e /etc/systemd/system/envsbot.service; then
  echo "KEEP existing /etc/systemd/system/envsbot.service"
  sudo diff -u /etc/systemd/system/envsbot.service /tmp/envsbot.service.new || true
else
  sudo install -m 0644 /tmp/envsbot.service.new /etc/systemd/system/envsbot.service
fi
sudo systemd-analyze verify /etc/systemd/system/envsbot.service
sudo systemctl daemon-reload
sudo systemctl enable --now envsbot.service
journalctl -u envsbot.service -f

envsbot systemd check now fails when a writable path would make the whole application tree writable. The rendered service derives only the required configuration/database/backup/export/runtime directories and accepts optional local environment overrides from /etc/default/envsbot.

Backups and Restore

Managed backups are ZIP archives stored below data/backups by default. When BACKUP_ON_START = True, the bot creates one startup backup per process start; this also covers service restarts. In addition, BACKUP_INTERVAL_HOURS = 24 keeps long-running instances fresh by creating a supervised managed backup whenever the newest archive reaches that age. Set the interval to 0 only if periodic backups are intentionally handled elsewhere; this also disables the stale-age health warning/admin alert for managed backups while leaving backup verification available. Archives include:

  • bot.db
  • config.py
  • vcard.py
  • chat_slang.csv
  • slang_additions.csv
  • slang_removals.csv
  • manifest.json

For hardened installations, set RUNTIME_DATA_DIR = "/var/lib/envsbot". vcard.py, chat_slang.csv, slang review queues and profile hash markers then stay writable without granting write access to the application checkout. If the setting is omitted, the historical application-root location is retained.

Commands:

,backup
,backup list
,backup show last
,restore last confirm

Restore is owner-only. Before changing runtime files, envsbot fully verifies the selected archive, stages every restore input and creates a checksum-verified safety backup. It then stops command handling, plugins, supervised workers, the outbox, message cache and database before replacing bot.db, the active config and writable support files. The old Python process is never resumed against restored state: after success, or after any failure that happened after runtime quiescing, envsbot exits with restart code 75 so the normal Restart=on-failure systemd unit starts a fresh process. A failed file replacement is rolled back from an exact snapshot taken after runtime shutdown; the verified safety backup is preserved as an additional recovery point. Legacy support-file copies inside the read-only source tree remain available for offline/manual recovery. Backup archives contain secrets and should be protected like config.py.

SQLite Maintenance

Use ,bot status for a compact safe online database and operational health check. Use ,bot status full for additional SQLite page details, detected room problems, plugin details, bounded-cache diagnostics, and the same compact supervised-task inventory as ,tasks all. The task section is deliberately last because it is usually the longest. Healthy rooms are not enumerated there; use ,rooms list all for the complete MUC inventory. Use ,tasks full all when per-task timestamps, restart counters and circuit details are needed.

Do not run VACUUM from inside the live bot process. Stop the bot first and perform maintenance manually:

systemctl stop envsbot.service

DB_PATH="data/bot.db"  # use the DB_FILE path from your config
sqlite3 "$DB_PATH" "PRAGMA integrity_check;"
sqlite3 "$DB_PATH" "PRAGMA optimize;"
sqlite3 "$DB_PATH" "VACUUM;"

systemctl start envsbot.service

See docs/maintenance.md.

Tests and CI

Install development dependencies and run the complete warning-strict test suite:

python3 -m venv .venv
source .venv/bin/activate
pip install -c constraints/python313.txt -r requirements.txt -r requirements-dev.txt
./scripts/test.sh

Use constraints/python312.txt instead when the environment runs Python 3.12. Dependency snapshots pin the complete transitive dependency closure. Reproduce the reviewed pins with scripts/update-constraints.sh, or deliberately refresh them with scripts/update-constraints.sh <3.12|3.13> --refresh; see constraints/README.md.

test.sh always runs every selected test with RuntimeWarning and DeprecationWarning treated as failures. Its default mode skips coverage collection only, which makes normal developer loops faster without reducing test coverage. Useful modes are:

./scripts/test.sh --coverage       # full suite + enforced 85% coverage floor
./scripts/test.sh --last-failed    # re-run the previous failures
./scripts/test.sh --durations 25   # run all tests and show the 25 slowest
./scripts/test.sh tests/plugins/rss

Run mutation tests with mutmut:

./scripts/mutmut.sh run
./scripts/mutmut.sh results
./scripts/mutmut.sh browse

The mutmut configuration in pyproject.toml explicitly lists the flat-layout source paths and disables coverage during mutant test runs. scripts/mutmut.sh deliberately unsets PYTHONPATH so the generated ./mutants checkout cannot be shadowed by the original sources. Use ./scripts/mutmut.sh fresh for a clean full run.

Drone CI is configured in .drone.yml.

Documentation

Regenerate the command reference after changing command metadata:

python scripts/generate_commands_md.py

Security Notes

  • Keep config.py private; it contains the bot password and optional API keys.
  • Use a dedicated XMPP account for the bot.
  • Give Owner/Superadmin roles only to trusted administrators.
  • Runtime config output redacts known secret values, but logs and local files should still be protected.
  • VACUUM and other SQLite rewrite operations should be run only while the bot is stopped.
  • Review loaded plugins before enabling them in public rooms.

License

This project is licensed under the GPL-3.0-only license. See LICENSE for details. Future versions of the GPL license are explicitly excluded.

See docs/README.md for the full documentation index, including deployment notes in docs/deployment.md.

About

envs pubnix/tilde XMPP bot. MIRROR FROM https://git.envs.net/envs/envsbot

envs.net

Topics

botpythonslixmppxmppxmpp-bot

Resources

Readme
GPL-3.0 license

Code of conduct

Code of conduct

Contributing

Contributing

Security policy

Security policy
Activity
Custom properties

Stars

3 stars

Watchers

0 watching

Forks

1 fork
Report repository

Releases

Contributors

Languages