lornkarios/yandex-turbo-pages

Release historydanger

There has been only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence of limited ongoing maintenance, though the package may be intentionally stable.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the single historical release, this materially raises abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap, although it is less serious for this small library than the stale activity.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, but its last push was over five years ago and therefore does not demonstrate active upkeep.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a modest transparency concern rather than evidence that the package is unsafe.