fyrts/chrome-devtools-protocol
The package includes a clear README, matching source repository, and a permissive MIT license. Workflow review found no dangerous triggers or audit findings, though action pinning remains a reproducibility gap.
78%
Total Score
83
100
67
Health Score Breakdown
All 40 recent commits came from one contributor, leaving maintenance continuity dependent on a single person and creating a real bus-factor concern.
The repository has no security policy, which leaves vulnerability reporting and response expectations undocumented; the active release history partly offsets this transparency gap.
Both workflows were analyzed successfully with no dangerous triggers or audit findings, but all 7 action references are unpinned, leaving build inputs less reproducible than they could be.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jakub Kulhan |
| Sam Feyaerts |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/process Version >=4.4.30 | — | — |
chrome-php/wrench Version ^1.3 | — | — |
guzzlehttp/guzzle Version ^6.3|^7.0 | — | — |
symfony/filesystem Version >=5.3 | — | — |
Weekly Downloads
Info
- Last Published
- 1 day ago
- Created
- 3 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.