blinq/ui

Release historydanger

The package has had no release in about three years, with all seven releases concentrated in its first day and none in the last 12 months. That strongly increases abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the roughly three-year release gap. This is strong evidence that maintenance has stopped or substantially slowed.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but this offers little supporting evidence of community use or review.

Repository archivedcaution

The linked repository is not archived, so it remains technically available for maintenance. However, its last push was about three years ago, which limits the reassurance this provides.

Security policycaution

The repository has no security policy. For a package that supplies application UI components and install-time behavior, this reduces transparency about how security issues should be reported.