jblyberg/locum-api

Release historydanger

The package has made only two releases, both in May 2017, with no release in the last nine years. This is strong evidence of an unmaintained dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no visible current maintenance.

Maintainerscaution

Only one registry account can publish releases, leaving little visible publishing redundancy. The linked repository is user-owned, so there is no organization backing shown to offset that narrow base.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone severe risk.

Security policycaution

The linked repository has no security policy, leaving no documented route for reporting or handling vulnerabilities in a package with no recent maintenance activity.