Package Health Score

76 / 100

security
No known security issues
popularity
Small
maintenance
Sustainable
community
Active

Explore Similar Packages

Popularity

Small

GitHub Stars: 1.3K
Forks: 245
Contributors: 70

Direct Usage Popularity

Based on project statistics from the GitHub repository for the PyPI package tahoe-lafs, we found that it has been starred 1,297 times.

Security

No known security issues

Security and license risk for latest version

Release Date: Jan 19, 2024
Direct Vulnerabilities: 0
C
0
H
0
M
0
L
Indirect Vulnerabilities: 0
C
0
H
0
M
0
L
License Risk: 0
H
0
M
0
L

All security vulnerabilities belong to production dependencies of direct and indirect packages.

License

GPL-3.0

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.

Security Policy

We found a way for you to contribute to the project! Looks like tahoe-lafs is missing a security policy.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

Keep your project free of vulnerabilities with Snyk

Maintenance

Sustainable

Commit Frequency

Open Issues: 0
Open PR: 21
Last Release: 10 months ago
Last Commit: 26 days ago

Further analysis of the maintenance status of tahoe-lafs based on released PyPI versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that tahoe-lafs demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Active

Readme: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 70
Funding: No

With more than 10 contributors for the tahoe-lafs repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Python Versions Compatibility: >=3.8, <3.13

Age: 9 years
Latest Release: 10 months ago
Dependencies: 29 Direct
Versions: 11
Maintainers: 3
Wheels: OS Independent

Readme

Free and Open Decentralized Data Store

Tahoe-LAFS (Tahoe Least-Authority File Store) is the first free software / open-source storage technology that distributes your data across multiple servers. Even if some servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security.

Table of contents

💡 About Tahoe-LAFS

Tahoe-LAFS helps you to store files while granting confidentiality, integrity, and availability of your data.

How does it work? You run a client program on your computer, which talks to one or more storage servers on other computers. When you tell your client to store a file, it will encrypt that file, encode it into multiple pieces, then spread those pieces out among various servers. The pieces are all encrypted and protected against modifications. Later, when you ask your client to retrieve the file, it will find the necessary pieces, make sure they haven’t been corrupted, reassemble them, and decrypt the result.

*The image is taken from meejah's* [blog](https://blog.torproject.org/tor-heart-tahoe-lafs) *post at Torproject.org.*

The client creates pieces (“shares”) that have a configurable amount of redundancy, so even if some servers fail, you can still get your data back. Corrupt shares are detected and ignored so that the system can tolerate server-side hard-drive errors. All files are encrypted (with a unique key) before uploading, so even a malicious server operator cannot read your data. The only thing you ask of the servers is that they can (usually) provide the shares when you ask for them: you aren’t relying upon them for confidentiality, integrity, or absolute availability.

Tahoe-LAFS was first designed in 2007, following the "principle of least authority", a security best practice requiring system components to only have the privilege necessary to complete their intended function and not more.

Please read more about Tahoe-LAFS architecture here.

✅ Installation

For more detailed instructions, read Installing Tahoe-LAFS.

Once tahoe --version works, see How to Run Tahoe-LAFS to learn how to set up your first Tahoe-LAFS node.

🐍 Python 2

Python 3.8 or later is required. If you are still using Python 2.7, use Tahoe-LAFS version 1.17.1.

🤖 Issues

Tahoe-LAFS uses the Trac instance to track issues. Please email jean-paul plus tahoe-lafs at leastauthority dot com for an account.

📑 Documentation

You can find the full Tahoe-LAFS documentation at our documentation site.

💬 Community

Get involved with the Tahoe-LAFS community:

Chat with Tahoe-LAFS developers at #tahoe-lafs channel on libera.chat IRC network or Slack.
Join our weekly conference calls with core developers and interested community members.
Subscribe to the tahoe-dev mailing list, the community forum for discussion of Tahoe-LAFS design, implementation, and usage.

🤗 Contributing

As a community-driven open source project, Tahoe-LAFS welcomes contributions of any form:

Before authoring or reviewing a patch, please familiarize yourself with the Coding Standard and the Contributor Code of Conduct.

🥳 First Contribution?

If you are committing to Tahoe for the very first time, it's required that you add your name to our contributor list in CREDITS. Please ensure that this addition has it's own commit within your first contribution.

🤝 Supporters

We would like to thank Fosshost for supporting us with hosting services. If your open source project needs help, you can apply for their support.

We are grateful to Oregon State University Open Source Lab for hosting tahoe-dev mailing list.

❓ FAQ

Need more information? Please check our FAQ page.

📄 License

You may use this package under the GNU General Public License, version 2 or, at your option, any later version. You may use this package under the Transitive Grace Period Public Licence, version 1.0, or at your choice, any later version. (You may choose to use this package under the terms of either license, at your option.) See the file COPYING.GPL for the terms of the GNU General Public License, version 2. See the file COPYING.TGPPL for the terms of the Transitive Grace Period Public Licence, version 1.0.

See TGPPL.PDF for why the TGPPL exists, graphically illustrated on three slides.

FAQs

What is tahoe-lafs?

secure, decentralized, fault-tolerant file store. Visit Snyk Advisor to see a full health score report for tahoe-lafs, including popularity, security, maintenance & community analysis.

Is tahoe-lafs popular?

The python package tahoe-lafs receives a total of 274 weekly downloads. As such, tahoe-lafs popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is tahoe-lafs well maintained?

We found indications that tahoe-lafs maintenance is sustainable demonstrating some project activity. We saw a total of 70 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is tahoe-lafs safe to use?

The python package tahoe-lafs was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 10 November-2024, at 23:51 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP