jacksleight/coast-doctrine

Maintainerscaution

Only one account has registry publishing access, leaving limited visible publishing redundancy; this is a mild maintenance-resilience concern for a user-owned project.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. This weakens evidence of ongoing maintenance, even though a recent registry release exists.

Repo popularitycaution

The repository has no stars or forks and only one watcher, providing little community validation; popularity is supporting evidence, so this is a minor caution rather than a decisive risk.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured, leaving a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy. This does not establish a dependency problem, but it reduces transparency about how vulnerabilities are handled.