lakshmaji/uniquecode

Release historydanger

The latest release was in April 2017, with no releases in the last 12 months and only three releases overall. This long period without published updates is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long release gap. The absence of recent work materially lowers confidence in ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This leaves fewer automated checks supporting a small, inactive project.

Repository archivedcaution

The repository is not archived, which is a meaningful positive, but it was last pushed in May 2021 and therefore does not offset the much longer period of inactivity.

Security policycaution

The repository has no security policy. For a package that generates one-time codes, this is a transparency and maintenance gap, although it is less severe than the inactivity evidence.