docs: point all project links at the real repository
- Replace placeholder/incorrect URLs with the actual Gitea repository https://git.dvscloud.net/dvs/purepycrypto - CHANGELOG: github.com/dvs/purepycrypto -> git.dvscloud.net/dvs/purepycrypto - README: PyPI badge -> Repository badge; real `git clone` URL in the source-install recipe; badges now link to the repository - README / pyproject.toml / setup.py / PKG-INFO: remove the unrelated https://apds.top homepage that did not belong to this project
This commit is contained in:
@@ -1,10 +1,10 @@
|
||||
# purepycrypto
|
||||
|
||||
[](https://pypi.org/project/purepycrypto/)
|
||||
[](https://git.dvscloud.net/dvs/purepycrypto)
|
||||
[](https://www.python.org/)
|
||||
[](./LICENSE)
|
||||
[](.)
|
||||
[-orange)](.)
|
||||
[](https://git.dvscloud.net/dvs/purepycrypto)
|
||||
[-orange)](https://git.dvscloud.net/dvs/purepycrypto)
|
||||
|
||||
> **Pure Python Cryptography Toolkit — a zero-dependency pure-Python cryptography library.**
|
||||
> SHA-2 / SHA-3 / SHAKE / BLAKE2b · PBKDF2 / HKDF / scrypt / Argon2id · AES (ECB/CBC/CTR/CFB/OFB/GCM) · AES-GCM-SIV · ChaCha20-Poly1305 / XChaCha20-Poly1305 · X25519 · Ed25519 · RSA-OAEP / PSS · PKCS#1 / PKCS#8 / SPKI / PEM
|
||||
@@ -159,7 +159,7 @@ pip install --upgrade purepycrypto
|
||||
Install from source (development mode):
|
||||
|
||||
```bash
|
||||
git clone <repo-url>
|
||||
git clone https://git.dvscloud.net/dvs/purepycrypto.git
|
||||
cd purepycrypto
|
||||
pip install -e .
|
||||
```
|
||||
@@ -790,7 +790,7 @@ This project is released under the **MIT License**. See [`LICENSE`](LICENSE) for
|
||||
**Dvs(DvsXT)** — self-developed cryptography library · purepycrypto
|
||||
|
||||
- Email: dvs6666@163.com
|
||||
- Project homepage: https://apds.top
|
||||
- Repository: https://git.dvscloud.net/dvs/purepycrypto
|
||||
|
||||
> 💡 **Disclaimer**: This library is designed for learning, experimentation, teaching, and embedded prototypes, and the author accepts no liability for any direct or indirect loss caused by its use.
|
||||
> For production-critical scenarios, please prefer implementations that have been widely audited and maintained by professional cryptography engineering teams.
|
||||
|
||||
Reference in New Issue
Block a user