simonmarcellinden/databasesettings

Release historydanger

The latest release was over 3 years ago, and there have been no releases in the last 12 months. This is strong evidence of an inactive project and outweighs its earlier release cadence.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap. No provided signal shows current maintenance capacity.

Maintainerscaution

The registry has one publishing maintainer, and project backing identifies an individual owner rather than an organization. This leaves limited visible maintainer redundancy alongside the inactive repository.

Repo popularitycaution

The repository has 0 stars and 0 forks, with 1 watcher. Popularity is only supporting evidence, but these figures provide no community-maintenance signal to offset the inactivity.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. That reduces ongoing supply-chain hygiene, although it is not evidence of a defect by itself.