devbr/pack-blog

Release historydanger

Only two releases were published, with none in the last 12 months; the latest release is more than eight years old. This is strong evidence of stagnation despite the short initial 11-day release interval.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. This is a transparency gap, though it is secondary to the much stronger maintenance concerns.

Version stabilitycaution

Version 0.0.2 is not a stable major release, so compatibility expectations are limited. Its lack of prerelease labeling is mildly positive but does not offset the very early version line.