pdfTeX

I Use This!

Low Activity

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

Project Summary

The main purpose of the pdfTeX project is to create and maintain an extension of TeX that can produce PDF directly from TeX source files and improve/enhance the result of TEX typesetting with the help of PDF. When PDF output is not selected, pdfTEX produces normal DVI output, otherwise it generates PDF output that looks identical to the DVI output.
An important aspect of this project is to investigate alternative justification algorithms (e. g. a font expansion algorithm akin to the hz micro--typography algorithm by Prof. Hermann Zapf), optionally making use of Multiple Master fonts.
pdfTEX is based on the original TeX sources and Web2c, and has been successfully compiled on Unix, Win32 and MSDOS systems.

In a Nutshell, pdfTeX...

...
has had 960 commits made by 7 contributors
representing 10,092,699 lines of code
...
is mostly written in C
with an average number of source code comments
...
has a well established, mature codebase
maintained by a small development team
with increasing Y-O-Y commits
...
took an estimated 3,074 years of effort (COCOMO model)
starting with its first commit in August, 2003
ending with its most recent commit 9 days ago

Quick Reference

Homepage

svn://tug.org/pdftex

Become the first manager for pdfTeX

Licenses

GNU General Public License v2.0 or later

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Forbidden

Sub-License

Hold Liable

Required

Distribute Original

Disclose Source

Include Copyright

State Changes

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...

...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
...
in 2016, 47% of companies did not have formal process in place to track OS code
...
by exploring contributors within projects, you can view details on every commit they have made to that project

About Project Security