4slv/yaml-config

Release historydanger

The latest release was over seven years ago, with no releases in the last 12 months. Its earlier history of 17 releases shows past activity but does not offset the prolonged stop.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, despite the repository being available. This is strong evidence that maintenance has stopped.

Maintainerscaution

One registry account has publish access. This is a small maintainer base, but the linked repository is owned by the same individual, so it is consistent with a small personal project rather than unexplained publishing access.

Project backingcaution

The registry namespace and repository owner are the same individual account, showing direct ownership rather than a mismatched project source. It does not provide organizational backing or additional maintenance capacity.

Repo issue activitycaution

There were no new issues or pull requests in the last month and no merged pull requests. The lack of activity is consistent with the broader inactivity, although open issue data is unavailable.