linkorb/extractor-cli
Organizational ownership, a matching repository, and a clear README provide useful continuity and transparency. However, the repository has no commits in the last three months, no security scanning, and the latest registry release dates to 2018; pin this version only if its dependencies remain compatible.
55%
Total Score
75
100
88
75
Health Score Breakdown
The package has had no releases in the last 12 months, and its latest release was in 2018, indicating a substantial maintenance gap. The repository was pushed more recently, which partly offsets but does not remove the concern.
There were no commits and no active maintainers in the last three months, which is a meaningful maintenance concern for a package whose registry release history is also old.
Composer is used as the build tool, but no security scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a minor transparency gap for a small CLI project.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 LinkORB Engineering |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/yaml Version ^4.0 | — | — |
symfony/console Version ^4.0 | — | — |
linkorb/connector Version ^1.0 | — | — |
linkorb/extractor Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 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.