fissible/transmark-pdf
Its MIT licensing, security policy, and clean workflow audit improve transparency. The small two-person contributor base and short project history leave less external validation.
82%
Total Score
67
100
79
100
Health Score Breakdown
The registry namespace and repository are owned by the same individual account, providing consistent ownership but no organizational redundancy.
The package is only 40 days old with three releases, so its maintenance history is still short, although releases have been regular during that period.
Two contributors are active, but one accounts for 19 of 24 commits, leaving maintenance substantially concentrated in one person.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest process gap.
Version v0.2.1 is not a stable major release, which signals an immature API and possible compatibility changes for adopters.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 dompdf/dompdf Version ^3.1 | — | — |
smalot/pdfparser Version ^2.12 | — | — |
fissible/transmark Version >=0.3 <1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 month ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.