bravoury/blog

Release historydanger

The package has had five releases, but none in the last 12 months and its latest release was nearly eight years ago. This strongly lowers confidence in ongoing maintenance.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push and release, this is strong evidence of abandonment risk.

Project backingcaution

The repository is owned by an individual account rather than an organization. This does not prove poor stewardship, but it provides less visible backing for a package with no recent activity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small package, but these figures provide no meaningful supporting adoption signal.

Repo toolingcaution

The repository uses Composer build tooling, which fits the package ecosystem, but it has no security scanning tools. This is a modest transparency and maintenance gap.