Analyzed
about 1 month
ago.
based on code collected
2 months
ago.
Project Summary
reposurgeon enables risky operations that version-control systems don't want to let you do, such as editing past comments and metadata, removing commits, splitting repositories, and joing repositories. It works with any version control system that can export and import git fast-import streams, including git and hg and bzr. Through plugins it can also handle Subversion, CVS, fossil, RCS, and darcs.
In a Nutshell, reposurgeon...
- ...
- ...
- ...
-
...
took an estimated 31 years of effort (COCOMO model)
starting with its first commit in February, 2009
ending with its most recent commit 6 months ago
Quick Reference
https://gitlab.com/esr/reposurge...
BSD 4-clause (University of California-Specific)
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Hold Liable
Use Trademarks
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.
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
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
anyone with an Open Hub account can update a project's tags
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
data presented on the Open Hub is available through our API
30 Day SummaryJan 1 2025 — Jan 31 2025
|
12 Month SummaryJan 31 2024 — Jan 31 2025
|
