blink/sentry

Release historydanger

The package has only one release, published over 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months. Combined with the single release over 10 years ago, this materially increases abandonment risk.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools are present. The missing scanning is a modest repository hygiene gap, not evidence that the package is unsafe by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a meaningful transparency gap for a package that handles error-reporting integration.

Version stabilitycaution

Version v0.2.0 is not a stable major release, although it is not marked as a prerelease. The versioning provides limited maturity evidence alongside the one-release history.