fyrts/chrome-devtools-pdf
It has a clear README, matching source tree, MIT licensing, and no install-time scripts. The single runtime dependency keeps the package simple, but there is no recent activity or security scanning.
58%
Total Score
63
100
78
88
Health Score Breakdown
One registry maintainer is consistent with the repository being owned by one user, but it leaves little visible maintainer capacity if that person stops maintaining the package.
The package has had four releases, but none in the last 12 months and the latest release was nearly four years ago, which raises abandonment concerns.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped.
There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet project, although it does not by itself distinguish stability from abandonment.
The repository has four stars and no forks, indicating limited adoption. Popularity is supporting evidence only, so this modestly reinforces the thin-project picture without deciding the result.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Sam Feyaerts |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 fyrts/chrome-devtools-protocol Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 7 years 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.