bregananta/anteraja

Release historydanger

The package has had only three releases, all clustered around June 2022, with no release in about four years. This is strong evidence of abandonment risk despite the stable 1.0.2 version.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the absence of recent releases. The project may be complete, but there is no observed maintenance capacity.

Maintainerscaution

One individual has registry publish access, leaving a thin publishing base. The linked repository is also user-owned rather than organization-backed, so there is limited visible continuity if that maintainer stops supporting it.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is less severe for a small courier API integration.