Go to file
Kieran Prasch 6e1113aa2d newsfrag for PR #3420 2024-02-13 10:53:03 -05:00
.github Build and push package to pypi whenever a release is published 2024-02-07 21:09:10 +01:00
deploy bump common python version to 3.12 2023-12-21 09:30:43 -05:00
examples repairs a p2p validity test that implements /ping. Linting. 2024-01-23 19:21:26 +01:00
newsfragments newsfrag for PR #3420 2024-02-13 10:53:03 -05:00
nucypher Updates remote regstry source url to reference the main branch on nucypher/nuypher github. 2024-02-13 10:53:03 -05:00
scripts Ignore lynx providers whose nodes are not running. 2024-02-13 10:53:03 -05:00
tests Update tests/acceptance/ape-config.yaml 2024-02-13 10:53:03 -05:00
.bumpversion.cfg Bump version: 7.1.0 → 7.2.0 2024-02-13 10:53:03 -05:00
.coveragerc Update coverage configuration to allow for better categorization of coverage reporting. 2022-11-14 18:07:53 -05:00
.dockerignore cloudworkers: clean disk space more thoroughly, stop containers first 2021-03-27 12:11:57 -07:00
.flake8 removes documentation build support. 2023-10-30 23:13:12 +01:00
.gitignore Move PRE examples to their own subfolder. 2023-09-28 11:53:20 -04:00
.pre-commit-config.yaml Modify darker to run with --check for push vs for commit. 2023-11-28 13:42:45 +01:00
CODE_OF_CONDUCT.md Add "end-of-file-fixer" to pre-commit hooks 2020-05-19 14:28:29 -04:00
CONTRIBUTING.rst removes docs building section from CONTRIBUTING.rst 2023-10-30 23:13:12 +01:00
LICENSE Relicense to AGPLv3 for more freedom 2019-03-04 18:55:28 -08:00
MANIFEST.in Cleanup build process 2024-02-07 21:09:10 +01:00
Makefile Cleanup build process 2024-02-07 21:09:10 +01:00
Pipfile Relock dependencies with prometheus-client as a primary dependency. 2024-01-23 13:27:35 +01:00
Pipfile.lock Relock dependencies with prometheus-client as a primary dependency. 2024-01-23 13:27:35 +01:00
README.md Update README.md 2023-10-30 23:13:12 +01:00
SECURITY.md removes documentation build support. 2023-10-30 23:13:12 +01:00
codecov.yml Fix code coverage to only focus on the `nucypher` folder. 2023-01-09 09:37:27 -05:00
dev-requirements.txt Relock dependencies with prometheus-client as a primary dependency. 2024-01-23 13:27:35 +01:00
mypy.ini Ignore setup.py in mypy configuration. 2020-05-28 11:59:47 -07:00
nucypher.png Relocate nucypher.png and releases.rst to the project root. 2023-10-30 23:13:12 +01:00
pyproject.toml Add rust to build toolchain 2024-02-07 21:09:10 +01:00
pytest.ini Run coverage directly and not through pytest-cov - there are discrepancy in reports. 2022-11-16 11:14:32 -05:00
releases.rst Updates release notes for v7.1.0 2024-01-30 13:33:52 +01:00
requirements.txt Relock dependencies with prometheus-client as a primary dependency. 2024-01-23 13:27:35 +01:00
setup.cfg Reconfigure setup.py; External deps, code cleanup, post install hook, installation options. 2020-05-28 11:59:08 -07:00
setup.py Cleanup build process 2024-02-07 21:09:10 +01:00
tox.ini Minimal example tox config for py36,37,38 2020-05-28 11:59:08 -07:00

README.md

Cryptographic primitives, hosted on the decentralized nodes of the Threshold network, offering accessible, intuitive, and extensible runtimes and interfaces for secrets management and dynamic access control.

pypi pyversions codecov discord license


TACo Access Control

TACo (Threshold Access Control) is end-to-end encrypted data sharing and communication, without the requirement of trusting a centralized authority, who might unilaterally deny service or even decrypt private user data. It is the only access control layer available to Web3 developers that can offer a decentralized service, through a live, well-collateralized and battle-tested network. See more here: https://docs.threshold.network/applications/threshold-access-control

Getting Involved

NuCypher is a community-driven project and we're very open to outside contributions.

All our development discussions happen in our Discord server, where we're happy to answer technical questions, discuss feature requests, and accept bug reports.

If you're interested in contributing code, please check out our Contribution Guide and browse our Open Issues for potential areas to contribute.

Security

If you identify vulnerabilities with any nucypher code, please email security@nucypher.com with relevant information to your findings. We will work with researchers to coordinate vulnerability disclosure between our stakers, partners, and users to ensure successful mitigation of vulnerabilities.

Throughout the reporting process, we expect researchers to honor an embargo period that may vary depending on the severity of the disclosure. This ensures that we have the opportunity to fix any issues, identify further issues (if any), and inform our users.

Sometimes vulnerabilities are of a more sensitive nature and require extra precautions. We are happy to work together to use a more secure medium, such as Signal. Email security@nucypher.com and we will coordinate a communication channel that we're both comfortable with.

A great place to begin your research is by working on our testnet. Please see our documentation to get started. We ask that you please respect testnet machines and their owners. If you find a vulnerability that you suspect has given you access to a machine against the owner's permission, stop what you're doing and immediately email security@nucypher.com.