Analyzed
about 20 hours
ago.
based on code collected
about 20 hours
ago.
Project Summary
TrackDown - Issue Tracking with plain Markdown. If you are missing the "git clone" for your tickets from github.com or bitbucket.org, then this is for you. A lightweight Ticketing System for distributed and unconnected small Teams.
In a Nutshell, trackdown...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in December, 2015
ending with its most recent commit 10 days ago
Quick Reference
https://github.com/mgoellnitz/tr...
GNU General Public License v3.0 only
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Use Patent Claims
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
Include Install Instructions
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
-
...
use of OSS increased in 65% of companies in 2016
-
...
check out hot projects on the Open Hub
30 Day SummarySep 26 2025 — Oct 26 2025
|
12 Month SummaryOct 26 2024 — Oct 26 2025
|
