osflab/db

Release historydanger

Only one release exists, published about eight years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained release line.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little current maintenance capacity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month. The null issue totals limit interpretation, but the observed absence of recent activity supports the maintenance concern.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide no evidence of a broad community that could compensate for inactive maintainers.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are configured. This is a hygiene gap that adds little independent risk compared with the stronger abandonment signals.