learningbird/lbconf

Release historydanger

The package has only one release, published nearly ten years ago, with no releases in the last 12 months. This is strong evidence that maintenance has effectively stopped.

Repo popularitycaution

The repository has zero stars and one fork, providing little supporting evidence of broad review or adoption. Popularity is only supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are present. That weakens ongoing supply-chain transparency, especially alongside the lack of recent maintenance evidence.

Repository archivedcaution

The repository is not marked archived, which avoids the strongest abandonment signal, but its last push was nearly ten years ago and does not offset the stale release history.

Security policycaution

The linked repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a real transparency gap, though not evidence that the package is malicious.