lndj/lcrawl

The repository remains linked, licensed, and unarchived, with a clear README and matching package source. Recent repository activity is absent and no security policy is provided, leaving maintenance and vulnerability reporting uncertain.

Latest v3.1.0

Packagist

52%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in nearly ten years, with zero releases in the last 12 months; its seven earlier releases were clustered in a short initial period. This is substantial evidence of release abandonment, even though the repository is not archived.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale registry release history, this materially raises the risk that fixes and updates will not arrive.

Repo issue activity

There is only one open issue and two open pull requests, with no issues or pull requests opened or merged in the last month. This indicates limited current interaction but is not, by itself, evidence of abandonment.

Repo tooling

The repository uses Composer for builds, which fits the package ecosystem, but it has no security scanning tools. The missing scanning is a modest transparency and maintenance concern rather than a standalone severe risk.

Security policy

No repository security policy is present, so there is no documented channel or process for reporting vulnerabilities. This weakens security maintenance transparency for a package that makes external web requests.