slidi/firework

Release historydanger

Only one release exists, published over four years ago, with no releases in the last 12 months. This is strong evidence of an inactive project and is not offset by the repository merely remaining available.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push and single-release history, this materially increases abandonment risk.

Project backingcaution

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides no organizational backing to offset the lack of recent activity.

Repo issue activitycaution

One issue and one pull request remain open, with no new or closed activity in the last month. This suggests limited responsiveness, though the small issue volume prevents treating it as conclusive alone.

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 little evidence of community adoption or review.