shieldfy/API-Security-Checklist

Checklist of the most important security countermeasures when designing, testing, and releasing your API

23.3k stars · 2.6k forks

This repo isn't software code, so code checks are limited.

Healthy

Healthy: maintained by 1 person in the last 90 days, no known risks.

Why

No rule fired.

What would change this

Maintenance

Complete

Steady

Human commits, 30 days
0
Human commits, 90 days
1
Human commits, 365 days
11
Bot share of commits, 365 days
0%
Last commit
Jul 21, 2026 (2 months ago)
Last human commit
Jul 21, 2026 (2 months ago)
Authors, 90 days
1
Last release
none found
Median PR merge time
6 hours

Responsiveness: of 0 recent issues, n/a got a maintainer reply. Median first response: n/a.

Sources: Commits, Releases, Merged pull requests, Issues

People

Complete
Owner
Organization
Commits sampled
11 since Oct 15, 2025
Authors for half of commits
2
Authors for 80% of commits
3
Contributors
85

Top committers

Sources: Commits, Contributors

Stars

Complete

Organic, confidence medium

Stars per week, 2017-07-02 to 2026-10-11. 25 weeks overlap a burst.Peak 5.2k a week2017-07-022026-10-11
Bars show stars gained each week. Orange bars overlap a burst.

Bursts

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

Sources: How star history is analyzed

Risk

Complete

Flags

License

Now
MIT (OSI-approved)
A year ago
MIT (OSI-approved)

Packages

No published packages found.

OpenSSF Scorecard: 3.0 out of 10 (via deps.dev).

Sources: GitHub: shieldfy/API-Security-Checklist

Badge

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/shieldfy/API-Security-Checklist/badge.svg)](https://reporadar.ai/shieldfy/API-Security-Checklist)

Earlier verdicts

Computed 2 hours ago · method 2026.10.2