byancode/remote-config

Repo commit activitydanger

There were no commits and no active maintainers during the last three months, which is direct evidence of dormant maintenance for a package released only in May 2025.

Release historycaution

All three releases arrived within roughly two hours in May 2025, with no releases in the following 12 months. That concentrated history provides limited evidence of continued maintenance.

Repo popularitycaution

The repository has zero stars and forks and one watcher. This is weak supporting evidence rather than a verdict, but it provides little external adoption signal alongside the inactive history.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are configured. That is a modest transparency and hygiene gap, not evidence that the release is unsafe.

Security policycaution

The repository has no security policy. For a package that stores application configuration, this reduces the available process transparency, though it is not a standalone adoption blocker.