AUTO-MAS MaaFW Adapter
通用 MFW 专项插件:托管 MaaFWConfig,用宿主迁来的脚本级管理器跑通一轮,并提供外壳配置导入的 3 个端点(/api/scripts/maafw/shell-instances、/import、/apply)。
依赖
auto-mas-core:插件 SDK。auto-mas-maafw-interface、auto-mas-maafw-native:两块库。auto-mas-maafw-agent-env、auto-mas-maafw-runner、auto-mas-maafw-project-update:三块服务插件。插件声明requires这三块的服务,0.1.0 还直接 import 它们的模块,所以依赖都写到次版本上限<0.2。
宿主必须是不再内置 MFW / M9A / MSS 的让位分支;仍内置时加载会报 ImportError。
0.1.0 的做法
- 执行:
expander.MaaFWExpander只是外壳,整轮交给manager.MaaFWEmbeddedManager。L2 已经持有托管 X 锁,管理器以「宿主已持锁」模式运行,_check里不再自己拿锁。 - 跨插件调用:真正走服务的只有属主登记(
maafw.project.v1的owner.register/owner.unregister,本插件提供maafw.owner.maafw_adapter.v1)。其余直接 import 三块服务插件的模块,全部写在函数体内,或者放在只会在函数体内首次导入的模块(manager、account_run、shell_api、shell_instances)里。 - 流程模块仍直接导入宿主的
app.*(app.models.schema的 MaaFW 模型、通知格式等),只在宿主进程里跑。
开发与测试
本地联调时把本仓库以目录联接放到联调宿主的 plugins/maafw_adapter。单元测试不随仓库提交。
Metadata
Release files for auto-mas-maafw-adapter 0.1.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 |
|---|---|---|---|---|
| auto_mas_maafw_adapter-0.1.0.tar.gz | 88.0 kB | With provenance | Details for auto_mas_maafw_adapter-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| auto_mas_maafw_adapter-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for auto_mas_maafw_adapter-0.1.0-py3-none-any.whl |
Total release size: 183.2 kB
Release files / auto_mas_maafw_adapter-0.1.0.tar.gz
| Download URL | auto_mas_maafw_adapter-0.1.0.tar.gz |
|---|---|
| Size | 88.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce2cb228fe2d14d304c92f1f39b23734900f9f5825da42424add732a788a6370
|
|
BLAKE2b-256 checksum How to use checksums |
7d43f502c2b740f55aa0159b17727dc8434386d7a1bc4729ba6e4b9e5c1a2f1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 22, 2026.
Transparency logRelease files / auto_mas_maafw_adapter-0.1.0-py3-none-any.whl
| Download URL | auto_mas_maafw_adapter-0.1.0-py3-none-any.whl |
|---|---|
| Size | 95.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d7996aeaff73574e01ed4a67f4e475c0d512bcc64b490bf30008b5ba6359d94
|
|
BLAKE2b-256 checksum How to use checksums |
49467b63109ce1bdd8506d88305745dea32a2ad2d80eb9a6b8e266d7c0a8f7ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 22, 2026.
Transparency logSecurity for auto-mas-maafw-adapter 0.1.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
Both files in this release have been uploaded with provenance metadata.
Attestation for auto_mas_maafw_adapter-0.1.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 Nov 22, 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.