try-again-later/pup

Release historycaution

Only four releases were published, all concentrated in August 2022, with no release in about four years and none in the last 12 months. This is a meaningful maintenance concern, though the repository was still pushed in June 2025.

Repo commit activitycaution

There were no commits and no active maintainers in the three months measured, consistent with a very low current maintenance tempo. The more recent push date is a partial counterweight, but not evidence of sustained activity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, so there is little community adoption evidence or outside review to support long-term confidence. Popularity is supporting evidence rather than a verdict.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This matters for a library intended to process application data, but it does not establish that the package is unsafe.