vanderlee/comprehend
The project has strong documentation, tests, a changelog, a clear MIT license, and a small runtime dependency surface. Recent repository work is concentrated in one maintainer, and workflow actions are unpinned; the missing security policy is a smaller transparency gap.
78%
Total Score
67
100
94
83
Health Score Breakdown
The repository is owned by a user rather than an organization, so the single-maintainer concentration is not offset by visible organizational handoff capacity.
Only three releases have been published and none appeared in the last 12 months, which raises a maintenance concern, although recent repository commits provide compensating evidence of ongoing work.
One contributor made all seven commits in the last three months, creating a genuine continuity risk for a user-owned project with no organizational backing shown.
No security policy is present, leaving vulnerability reporting and response expectations undocumented; this is a modest transparency gap rather than evidence of unsafe code.
The workflow is fully analyzed, uses read-only permissions, and has no audited findings, but both action references are unpinned, weakening reproducibility and update integrity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 8 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.