znkaz/base

Release historydanger

The package has only one release, published about five years ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, consistent with the long gap since the last repository push and increasing abandonment risk.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of broad adoption.

Repo toolingcaution

The repository uses Composer, but no security-scanning tools were detected. The build setup is present while automated security coverage is limited.

Security policycaution

The repository has no security policy. This is a transparency and reporting gap, though it is less decisive for a small package than the lack of maintenance activity.