nonebot-plugin-asf
NoneBot plugin for controlling ArchiSteamFarm through Telegram and ASF IPC.
Runtime Model
Load nonebot_plugin_asf from a NoneBot app. The plugin handles Telegram Bot
API long polling directly and forwards authorized ! commands to ASF IPC.
Configuration
Set these environment variables:
ASF__TELEGRAM_BOT_TOKENASF__TELEGRAM_PROXY, optional HTTP or SOCKS proxy URL for Telegram API accessASF__TELEGRAM_ALLOWED_USER_IDS, comma-separated Telegram user IDsASF__TELEGRAM_ALLOWED_CHAT_IDS, optional comma-separated chat IDsASF__BASE_URL, defaulthttp://asf:1242ASF__IPC_PASSWORDASF__POLL_TIMEOUT_SECONDS, default45
At least one of ASF__TELEGRAM_ALLOWED_USER_IDS or
ASF__TELEGRAM_ALLOWED_CHAT_IDS must be set.
Usage
/helpshows wrapper usage./commandslists ASF commands and is registered in Telegram's bot menu.- ASF commands require
!, for example!status.
1 maintainer
Metadata
1 maintainer
Release files for nonebot-plugin-asf 0.2.0
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 |
|---|---|---|---|---|
| nonebot_plugin_asf-0.2.0.tar.gz | 5.9 kB | With provenance | Details for nonebot_plugin_asf-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nonebot_plugin_asf-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for nonebot_plugin_asf-0.2.0-py3-none-any.whl |
Total release size: 12.3 kB
Release files / nonebot_plugin_asf-0.2.0.tar.gz
| Download URL | nonebot_plugin_asf-0.2.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08f897db02599ad3466252508fc2538f70d346e2996c31efaf0bb3a4ab790d0a
|
|
BLAKE2b-256 checksum How to use checksums |
c5b1af16fb2a0da809616dfab8f485b17b0bbcdfecbf5f555ff29fa15b7497b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logRelease files / nonebot_plugin_asf-0.2.0-py3-none-any.whl
| Download URL | nonebot_plugin_asf-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
552904d6f6afbfd11162371bf0e6c9b4493a0911b11ccf93ce972f4392383821
|
|
BLAKE2b-256 checksum How to use checksums |
ffe48f730ce23f447dc66ca0c12208b791e4fc38632e7d5bc7d1bbd571b28e22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logSecurity for nonebot-plugin-asf 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for nonebot_plugin_asf-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logA 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.
