gurkanbicer/getdns

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, with its last push around September 2024. This strongly increases the risk that defects or dependency changes will go unattended.

Project backingcaution

The package and repository are owned by the same individual account rather than an organization. This is consistent ownership, but it offers less visible backing capacity for long-term maintenance.

Release historycaution

The package has only three releases, all clustered in September 2024, with no release in about two years. This is a meaningful maintenance concern for a dependency.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small utility, but it provides little evidence of broad review or community support.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than proof of unsafe code.