reddingwebdev/abuseipdb

Release historycaution

The package is less than one day old with only two releases, so there is too little history to establish sustained maintenance. The rapid second release is a small positive but does not offset the limited track record.

Repo commit activitycaution

There were no commits or active maintainers in the measured three-month window. Because the repository was created very recently, this is partly explained by its age, but it still provides no evidence of sustained maintenance yet.

Security policycaution

The repository has no security policy. For a client handling API credentials and external HTTP calls, this is a transparency gap, although it is not evidence that the package is unsafe by itself.

Version stabilitycaution

Version 0.1.1 is not a prerelease, but it is still below a stable major version and the package has no established release history. This indicates a potentially changing API rather than an immediate abandonment risk.

Workflow auditcaution

The single workflow was fully analyzed with no untrusted checkouts, script injection, or audit findings, but all 11 action references are unpinned. Missing top-level permissions is acceptable here, while unpinned actions reduce build reproducibility and supply-chain hygiene.