mikycorp/registry

Release historydanger

The package has only two releases, both from May 2017, and none in the last 12 months. This long period without releases is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2017.

Package scaffoldingcaution

The artifact includes a README, but it is only 10 characters long and provides almost no consumer guidance. The absence of tests and a changelog in the published artifact is normal packaging practice and is not a concern by itself.

Repo toolingcaution

Composer is used for the build, but no security-scanning tool is configured. This is a hygiene gap that adds uncertainty about how dependency or release issues would be detected.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more for an unmaintained package because there is little evidence of ongoing oversight.