mlebkowski/crane

Release historydanger

The package has only two releases, with the latest published nearly 13 years ago and no releases in the last 12 months. This indicates severe abandonment risk despite the short initial release interval.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package’s long release gap and leaving no evidence of ongoing maintenance.

Licensecaution

No registry license declaration or license file was detected in the package or repository. This creates a real adoption and redistribution concern for a dependency.

Maintainerscaution

Only one registry account has publishing access, leaving a thin publishing base. The matching user-owned repository provides provenance, but no broader maintainer capacity is shown.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This compounds the lack of current maintenance evidence.