SafeWrite

I Use This!

Inactive

Analyzed about 17 hours ago. based on code collected about 17 hours ago.

Project Summary

Provides a simple library for atomic update of files (mostly aimed at configuration files). Regardless of what might happen in the system, the library assures the user that either the complete old or complete new version of the file will be present on disk.

In a Nutshell, SafeWrite...

...
has had 41 commits made by 2 contributors
representing 220 lines of code
...
is mostly written in C
with a very well-commented source code
...
has a young, but established codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in December, 2010
ending with its most recent commit almost 12 years ago

Quick Reference

Project Links:

Homepage

Code Locations:

https://github.com/Shachar/safew...

Similar Projects:

Managers:

Shachar Shemesh

Licenses

MIT License

Permitted

Commercial Use

Modify

Distribute

Sub-License

Private Use

Forbidden

Hold Liable

Required

Include Copyright

Include License

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
use of OSS increased in 65% of companies in 2016
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
...
55% of companies leverage OSS for production infrastructure
...
by exploring contributors within projects, you can view details on every commit they have made to that project

About Project Security