becklyn/cert-key-matcher

Release historydanger

The package has only two releases, with the latest published in May 2020 and none in more than six years. That long period without releases raises abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, with the last repository push more than six years ago. This is the strongest evidence of abandonment risk.

Repo popularitycaution

The repository has one star, no forks, and two watchers, indicating very limited adoption and little visible community support. This increases reliance on the small maintainer base if problems arise.

Repo toolingcaution

Composer is used for builds, but no security-scanning tool is configured. The missing scanner is a modest transparency and maintenance gap, not evidence of a defect by itself.

Security policycaution

The repository has no security policy. For a small CLI tool this is not severe on its own, but it leaves vulnerability-reporting and response expectations unclear.