masterkey/shield

Release historydanger

The package has had no releases in the last 12 months, and its latest release was published about ten years ago. This is strong evidence of abandonment risk despite the package not being deprecated.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the release history showing no updates for about ten years. This materially increases 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 values provide no meaningful external evidence of active use or review.

Repo toolingcaution

Composer is used for builds, but the repository has no security-scanning tooling. Given the package's security-focused purpose, this is a meaningful transparency and maintenance gap.

Security policycaution

The repository has no security policy. For a package intended to improve application security, the absence of documented vulnerability-reporting guidance reduces transparency.