openclerk/config
The repository is correctly linked and licensed, with a usable README and no install-time scripts. Organization backing and the absence of deprecation help, but the tiny project has no security policy and shows little evidence of active use.
38%
Total Score
50
71
50
Health Score Breakdown
Only two releases exist, with the latest published about 11 years ago and none in the past 12 months. This is strong evidence of abandonment for a library dependency.
The repository recorded no commits and no active maintainers in the past three months, while its last push was about 9 years ago. The long-term inactivity is not offset by the repository remaining unarchived.
The repository has 0 stars, 3 forks, and 1 watcher, indicating very limited visible adoption. Popularity is supporting evidence rather than decisive, but it provides little reassurance alongside the inactive history.
No security policy is present in the repository. This is a transparency and maintenance gap, although it is less important than the prolonged lack of releases and commits.
Version 0.1.1 is not a stable-major release, so API compatibility may be less predictable. This is secondary to the much stronger concern that development has stopped.
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
- 11 years ago
- Created
- 11 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.