guiz/bbcodeparser

Release historydanger

The package has had only three releases, all starting about 8 years and 7 months ago, with none in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0.2 version.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent releases. No stronger maintenance signal compensates for this inactivity.

Repo popularitycaution

The repository has zero stars, one fork, and one watcher, providing little supporting evidence of an active user or maintainer community. Popularity is only supporting evidence, so this reinforces rather than determines the score.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. The absence is a modest transparency and maintenance concern rather than a severe risk on its own.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more because the project also shows no recent maintenance activity.