@huo15/huo15-huihuoyun-odoo
火一五·辉火云企业套件插件 — 自然语言操作辉火云企业套件,企业级全场景 ERP + 系统管理 + Studio 元编程 + 工具分级助手,**204 个工具**(含 odoo_help)覆盖销售/采购/库存/生产/会计/HR/项目/CRM/客服/知识/通知/智能/报表 13 业务域 + 系统级(自动化/治理/批量/集成)+ Studio 元编程;v1.10 共享凭据;v1.11–v1.13 HR 三步走;v1.14 Analytics & Orchestration;v1.15 个人视图+CRM 智能+
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 0 / 1 | |
| 1.23.1 | 0 / 1 | |
| 1.23.0 | 0 / 1 | |
| 1.22.0 | 0 / 1 | |
| 1.21.0 | 0 / 1 | |
| 1.20.2 | 0 / 1 | |
| 1.20.1 | 0 / 1 | |
| 1.20.0 | 0 / 1 | |
| 1.19.0 | 0 / 1 | |
| 1.18.0 | 0 / 1 | |
| 1.17.0 | 0 / 1 | |
| 1.16.0 | 0 / 1 | |
| 1.15.0 | 0 / 1 | |
| 1.14.0 | 0 / 1 | |
| 1.13.0 | 0 / 1 | |
| 1.12.0 | 0 / 1 | |
| 1.11.0 | 0 / 1 | |
| 1.10.0 | 0 / 1 | |
| 1.9.0 | 0 / 1 | |
| 1.8.0 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.6.1 | 0 / 1 | |
| 1.6.0 | 0 / 1 | |
| 1.3.1 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.1 | 0 / 1 | |
| 1.1.0 | 0 / 1 |
v1.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.