ccs-selfcheck — 自主创新第一件产品（2026-11-04 21:57 授权后）
定位
one-file 自查 CLI（纯 stdlib）：MCP server 配置/工具面 → 五类参数风险分级 → 签名样例 receipt。 获客逻辑：自建 gateway/policy 的工程师（aiwcorpo 类，GitHub 上 30 天 740 个新 gateway）自己跑一遍，看到自己工具面的 HIGH 清单 + 一张真形态的签名 receipt——产品教育在用户自己机器上完成，零销售介入。
差异化
- 不装包不注册：
python ccs_selfcheck.py --demo十秒出结果 - 产物是真 receipt（Ed25519/JCS/chain 结构与正式产品一致），不是"风险报告 PDF"
- 明确不收集、不上传——一切本地
状态
- 本地完成并自验收（demo 4 用例：1 LOW / 3 HIGH，3 张签名样例落盘）✅
- PyPI 名
ccs-selfcheck可用 - 未做：PyPI 发布（需要 neuralbridge 令牌或用户 PyPI 账号操作）、GitHub 公开仓
1 maintainer
Metadata
1 maintainer
Release files for ccs-selfcheck 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ccs_selfcheck-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ccs_selfcheck-0.1.0-py3-none-any.whl |
Release files / ccs_selfcheck-0.1.0-py3-none-any.whl
| Download URL | ccs_selfcheck-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa76cb4a2b7e871b5d42dc8d97c1c9f5c02e51e2b95a2d414df37b3ffc60950a
|
|
BLAKE2b-256 checksum How to use checksums |
34a3515bf3b0fd0248bbd010fe1bec177193af880143111ed405c9a3199adcf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Security for ccs-selfcheck 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.
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.
