nerd-components/nerd-proxy

Release historydanger

Only one release exists, published about nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package not being formally deprecated.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, while the repository was last pushed about nine years ago. This substantially increases abandonment and compatibility risk.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no supporting evidence of community adoption or external maintenance. Popularity is not required for health, so this is a secondary concern.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. This is a modest transparency and maintenance gap, not a severe risk on its own.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The lack of a policy matters more given the absence of recent maintenance activity.