mcpsafetywarden vs airbyte-source-pokeapi — Trust Score Comparison
Side-by-side trust comparison of mcpsafetywarden and airbyte-source-pokeapi. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
arden — Nerq Trust Score 53.5/100 (C-). airbyte-source-pokeapi — Nerq Trust Score 63.5/100 (C+). airbyte-source-pokeapi leads by 10.0 points.
Detailed Score Analysis
| Dimension | arden | airbyte-source-pokeapi |
|---|---|---|
| Security | 90/100 | 90/100 |
| Maintenance | 51/100 | 91/100 |
| Popularity | 0/100 | 0/100 |
| Quality | 65/100 | 65/100 |
| Community | 35/100 | 35/100 |
Five-dimension Nerq trust breakdown (registries: pypi / pypi). Scored equally weighted across security, maintenance, popularity, quality, community.
Detailed Metric Comparison
| Metric | mcpsafetywarden | airbyte-source-pokeapi |
|---|---|---|
| Trust Score | 69.0/100 | 53.0/100 |
| Grade | B- | D |
| Stars | 0 | 0 |
| Category | uncategorized | uncategorized |
| Security | N/A | N/A |
| Compliance | N/A | 100 |
| Maintenance | N/A | N/A |
| Documentation | N/A | N/A |
| EU AI Act Risk | N/A | N/A |
| Verified | No | No |
Verdict
mcpsafetywarden leads with a trust score of 69.0/100 compared to airbyte-source-pokeapi's 53.0/100 (a 16.0-point difference). Both agents should be evaluated based on your specific requirements.
Detailed Score Analysis
Five-dimensional trust breakdown for mcpsafetywarden (pypi) and airbyte-source-pokeapi (pypi) from Nerq’s enrichment pipeline. All 5 dimensions scored on 0–100 scales, refreshed every 7 days, covering 5M+ indexed assets across 14 registries.
| Dimension | mcpsafetywarden | airbyte-source-pokeapi |
|---|---|---|
| Security | 90/100 | 90/100 |
| Maintenance | 51/100 | 91/100 |
| Popularity | 0/100 | 0/100 |
| Quality | 65/100 | 65/100 |
| Community | 35/100 | 35/100 |
5-Dimension Breakdown
Security — mcpsafetywarden vs airbyte-source-pokeapi
Security aggregates dependency vulnerability scans, known CVE exposure, supply-chain hygiene, and adherence to security best practices. On this dimension mcpsafetywarden scores 90/100 (top-tier) while airbyte-source-pokeapi scores 90/100 (top-tier). The two are effectively tied on security (both at 90/100). The mcpsafetywarden figure is derived from its pypi registry footprint; the airbyte-source-pokeapi figure from pypi. For a pypi/pypi cross-registry pair, a security score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. A score above 85 implies a clean dependency tree with 0 critical CVEs in the last 90 days; 70–84 tolerates 1–2 medium-severity issues; below 55 usually flags 3+ unresolved advisories. Given the current 90/100 for mcpsafetywarden and 90/100 for airbyte-source-pokeapi, the combined midpoint is 90.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Maintenance — mcpsafetywarden vs airbyte-source-pokeapi
Maintenance captures commit cadence, issue turnaround, release frequency, and the health of the project’s active contributor base. On this dimension mcpsafetywarden scores 51/100 (below-average) while airbyte-source-pokeapi scores 91/100 (top-tier). airbyte-source-pokeapi leads by 40 points (91/100 vs 51/100), a spread wide enough that teams should weight maintenance heavily when choosing. The mcpsafetywarden figure is derived from its pypi registry footprint; the airbyte-source-pokeapi figure from pypi. For a pypi/pypi cross-registry pair, a maintenance score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. Scores above 80 correspond to release cadences of 30 days or less and median issue-response times under 7 days; below 50 often means no release in 180+ days. Given the current 51/100 for mcpsafetywarden and 91/100 for airbyte-source-pokeapi, the combined midpoint is 71.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Popularity — mcpsafetywarden vs airbyte-source-pokeapi
Popularity measures adoption signals—weekly downloads, dependent packages, GitHub stars, and cross-registry citation density. On this dimension mcpsafetywarden scores 0/100 (weak) while airbyte-source-pokeapi scores 0/100 (weak). The two are effectively tied on popularity (both at 0/100). The mcpsafetywarden figure is derived from its pypi registry footprint; the airbyte-source-pokeapi figure from pypi. For a pypi/pypi cross-registry pair, a popularity score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. A score of 90+ indicates the top 1% of the registry by dependent count or weekly downloads; 70–89 is the top 10%; below 40 suggests fewer than 500 weekly downloads. Given the current 0/100 for mcpsafetywarden and 0/100 for airbyte-source-pokeapi, the combined midpoint is 0.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Quality — mcpsafetywarden vs airbyte-source-pokeapi
Quality evaluates documentation completeness, test coverage indicators, typed-API availability, and the presence of examples or tutorials. On this dimension mcpsafetywarden scores 65/100 (mid-band) while airbyte-source-pokeapi scores 65/100 (mid-band). The two are effectively tied on quality (both at 65/100). The mcpsafetywarden figure is derived from its pypi registry footprint; the airbyte-source-pokeapi figure from pypi. For a pypi/pypi cross-registry pair, a quality score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. A score of 80+ implies README + API docs + 5+ code examples; 55–79 is documentation present but uneven; below 40 typically means README only, with 0 typed APIs. Given the current 65/100 for mcpsafetywarden and 65/100 for airbyte-source-pokeapi, the combined midpoint is 65.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Community — mcpsafetywarden vs airbyte-source-pokeapi
Community looks at contributor breadth, issue-response participation, Stack Overflow answer volume, and third-party tutorial ecosystem. On this dimension mcpsafetywarden scores 35/100 (weak) while airbyte-source-pokeapi scores 35/100 (weak). The two are effectively tied on community (both at 35/100). The mcpsafetywarden figure is derived from its pypi registry footprint; the airbyte-source-pokeapi figure from pypi. For a pypi/pypi cross-registry pair, a community score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. Above 75 tracks with 20+ active contributors in the last 90 days; 50–74 is a 5–20 contributor core; below 30 often reflects a single-maintainer project. Given the current 35/100 for mcpsafetywarden and 35/100 for airbyte-source-pokeapi, the combined midpoint is 35.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Score-Card Summary
Across the 5 measured dimensions, mcpsafetywarden averages 48.2/100 (range 0–90) and airbyte-source-pokeapi averages 56.2/100 (range 0–91). mcpsafetywarden leads on 0 dimensions, airbyte-source-pokeapi leads on 1, with 4 tied.
| Band | Range | mcpsafetywarden dims | airbyte-source-pokeapi dims |
|---|---|---|---|
| Top-tier | 85–100 | 1 | 2 |
| Strong | 70–85 | 0 | 0 |
| Mid-band | 55–70 | 1 | 1 |
| Below-avg | 40–55 | 1 | 0 |
| Weak | 0–40 | 2 | 2 |
Scoring scale: 0–39 weak, 40–54 below-average, 55–69 mid-band, 70–84 strong, 85–100 top-tier. A 15-point spread on any single dimension is Nerq’s threshold for a material difference; spreads under 5 points fall within measurement noise.
Head-to-Head Deltas
| Dimension | mcpsafetywarden | airbyte-source-pokeapi | Delta | Leader |
|---|---|---|---|---|
| Security | 90 | 90 | +0 | tied |
| Maintenance | 51 | 91 | -40 | airbyte-source-pokeapi |
| Popularity | 0 | 0 | +0 | tied |
| Quality | 65 | 65 | +0 | tied |
| Community | 35 | 35 | +0 | tied |
Combined 5-dimension average: mcpsafetywarden 48.2/100, airbyte-source-pokeapi 56.2/100, overall spread -8.0 points.
- Max spread: 40 points on Maintenance
- Min spread: 0 points on Security
- Dimensions within 10 points: 4/5
- mcpsafetywarden above 70 on: 1/5 dimensions
- airbyte-source-pokeapi above 70 on: 2/5 dimensions
Detailed Analysis
Community & Adoption
mcpsafetywarden has 0 GitHub stars while airbyte-source-pokeapi has 0. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose mcpsafetywarden if you need:
- Higher overall trust score — more reliable for production use
Choose airbyte-source-pokeapi if you need:
- Consider if it better fits your specific use case
Switching from mcpsafetywarden to airbyte-source-pokeapi (or vice versa)
When migrating between mcpsafetywarden and airbyte-source-pokeapi, consider these factors:
- API Compatibility: mcpsafetywarden (uncategorized) and airbyte-source-pokeapi (uncategorized) share similar interfaces since they are in the same category.
- Security Review: Run a security audit after migration. Check the mcpsafetywarden safety report and airbyte-source-pokeapi safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: mcpsafetywarden has 0 stars and airbyte-source-pokeapi has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-05-13 | Data refreshed weekly
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.