navarr/binary-explode

Release historycaution

The package has existed for about 9 years but has only 6 releases, with one release in the last 12 months and the latest nearly a year ago. This indicates a slow cadence, though the project is not abandoned based on release history alone.

Repo commit activitycaution

There were no commits and no active maintainers in the last 3 months, while the latest repository push was nearly a year ago. This is a meaningful maintenance concern, despite the recent release history.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For this small package that is a modest transparency gap rather than evidence of unfitness.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's small scope and other repository evidence partly limit the concern.

Workflow auditcaution

Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, or audit findings, and no workflow has top-level write permissions. However, all 19 action references are unpinned, which leaves avoidable build-integrity risk.