babel-preset-jest vs inquirer-search-list — Trust Score Comparison

Side-by-side trust comparison of babel-preset-jest and inquirer-search-list. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.

babel-preset-jest scores 48.9/100 (D+) while inquirer-search-list scores 60.0/100 (C) on the Nerq Trust Score. inquirer-search-list leads by 11.1 points. babel-preset-jest is a uncategorized agent with 0 stars. inquirer-search-list is a uncategorized agent with 0 stars.

babel-preset-jest — Nerq Trust Score 69.5/100 (B-). search — Nerq Trust Score 79.5/100 (B+). search leads by 10.0 points.

48.9
D+
Categoryuncategorized
Stars0
Sourcenpm_full
Compliance100
vs
60.0
C
Categoryuncategorized
Stars0
Sourcenpm_full
Compliance100

Detailed Score Analysis

Dimensionbabel-preset-jestsearch
Security90/10090/100
Maintenance100/10097/100
Popularity0/100100/100
Quality65/10055/100
Community60/10045/100

Five-dimension Nerq trust breakdown (registries: npm / npm). Scored equally weighted across security, maintenance, popularity, quality, community.

Detailed Metric Comparison

Metric babel-preset-jest inquirer-search-list
Trust Score48.9/10060.0/100
GradeD+C
Stars00
Categoryuncategorizeduncategorized
SecurityN/AN/A
Compliance100100
MaintenanceN/AN/A
DocumentationN/AN/A
EU AI Act RiskN/AN/A
VerifiedNoNo

Verdict

inquirer-search-list leads with a trust score of 60.0/100 compared to babel-preset-jest's 48.9/100 (a 11.1-point difference). Both agents should be evaluated based on your specific requirements.

Based on our analysis, babel-preset-jest scores higher in Community (60/100) while inquirer-search-list is stronger in Popularity (100/100).

Detailed Score Analysis

Five-dimensional trust breakdown for babel-preset-jest (npm) and inquirer-search-list (npm) from Nerq’s enrichment pipeline. All 5 dimensions scored on 0–100 scales, refreshed every 7 days, covering 5M+ indexed assets across 14 registries.

Dimensionbabel-preset-jestinquirer-search-list
Security90/10090/100
Maintenance100/10097/100
Popularity0/100100/100
Quality65/10055/100
Community60/10045/100

5-Dimension Breakdown

Security — babel-preset-jest vs inquirer-search-list

Security aggregates dependency vulnerability scans, known CVE exposure, supply-chain hygiene, and adherence to security best practices. On this dimension babel-preset-jest scores 90/100 (top-tier) while inquirer-search-list scores 90/100 (top-tier). The two are effectively tied on security (both at 90/100). The babel-preset-jest figure is derived from its npm registry footprint; the inquirer-search-list figure from npm. For a npm/npm 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 babel-preset-jest and 90/100 for inquirer-search-list, the combined midpoint is 90.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.

Maintenance — babel-preset-jest vs inquirer-search-list

Maintenance captures commit cadence, issue turnaround, release frequency, and the health of the project’s active contributor base. On this dimension babel-preset-jest scores 100/100 (top-tier) while inquirer-search-list scores 97/100 (top-tier). babel-preset-jest leads by 3 points (100/100 vs 97/100), a narrow margin within measurement noise. The babel-preset-jest figure is derived from its npm registry footprint; the inquirer-search-list figure from npm. For a npm/npm 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 100/100 for babel-preset-jest and 97/100 for inquirer-search-list, the combined midpoint is 98.5/100 — useful as a portfolio-level proxy when both tools coexist in a stack.

Popularity — babel-preset-jest vs inquirer-search-list

Popularity measures adoption signals—weekly downloads, dependent packages, GitHub stars, and cross-registry citation density. On this dimension babel-preset-jest scores 0/100 (weak) while inquirer-search-list scores 100/100 (top-tier). inquirer-search-list leads by 100 points (100/100 vs 0/100), a spread wide enough that teams should weight popularity heavily when choosing. The babel-preset-jest figure is derived from its npm registry footprint; the inquirer-search-list figure from npm. For a npm/npm 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 babel-preset-jest and 100/100 for inquirer-search-list, the combined midpoint is 50.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.

Quality — babel-preset-jest vs inquirer-search-list

Quality evaluates documentation completeness, test coverage indicators, typed-API availability, and the presence of examples or tutorials. On this dimension babel-preset-jest scores 65/100 (mid-band) while inquirer-search-list scores 55/100 (mid-band). babel-preset-jest leads by 10 points (65/100 vs 55/100), a moderate gap that matters when quality is a hard requirement. The babel-preset-jest figure is derived from its npm registry footprint; the inquirer-search-list figure from npm. For a npm/npm 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 babel-preset-jest and 55/100 for inquirer-search-list, the combined midpoint is 60.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.

Community — babel-preset-jest vs inquirer-search-list

Community looks at contributor breadth, issue-response participation, Stack Overflow answer volume, and third-party tutorial ecosystem. On this dimension babel-preset-jest scores 60/100 (mid-band) while inquirer-search-list scores 45/100 (below-average). babel-preset-jest leads by 15 points (60/100 vs 45/100), a spread wide enough that teams should weight community heavily when choosing. The babel-preset-jest figure is derived from its npm registry footprint; the inquirer-search-list figure from npm. For a npm/npm 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 60/100 for babel-preset-jest and 45/100 for inquirer-search-list, the combined midpoint is 52.5/100 — useful as a portfolio-level proxy when both tools coexist in a stack.

Score-Card Summary

Across the 5 measured dimensions, babel-preset-jest averages 63.0/100 (range 0–100) and inquirer-search-list averages 77.4/100 (range 45–100). babel-preset-jest leads on 3 dimensions, inquirer-search-list leads on 1, with 1 tied.

BandRangebabel-preset-jest dimsinquirer-search-list dims
Top-tier85–10023
Strong70–8500
Mid-band55–7021
Below-avg40–5501
Weak0–4010

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

Dimensionbabel-preset-jestinquirer-search-listDeltaLeader
Security9090+0tied
Maintenance10097+3babel-preset-jest
Popularity0100-100inquirer-search-list
Quality6555+10babel-preset-jest
Community6045+15babel-preset-jest

Combined 5-dimension average: babel-preset-jest 63.0/100, inquirer-search-list 77.4/100, overall spread -14.4 points.

Detailed Analysis

Community & Adoption

babel-preset-jest has 0 GitHub stars while inquirer-search-list has 0. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.

When to Choose Each Tool

Choose babel-preset-jest if you need:

  • Consider if it better fits your specific use case

Choose inquirer-search-list if you need:

  • Higher overall trust score — more reliable for production use

Switching from babel-preset-jest to inquirer-search-list (or vice versa)

When migrating between babel-preset-jest and inquirer-search-list, consider these factors:

  1. API Compatibility: babel-preset-jest (uncategorized) and inquirer-search-list (uncategorized) share similar interfaces since they are in the same category.
  2. Security Review: Run a security audit after migration. Check the babel-preset-jest safety report and inquirer-search-list safety report for known issues.
  3. Testing: Ensure your test suite covers all integration points before switching in production.
  4. Community Support: babel-preset-jest has 0 stars and inquirer-search-list has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
babel-preset-jest Safety Report inquirer-search-list Safety Report babel-preset-jest Alternatives inquirer-search-list Alternatives

Related Pages

Frequently Asked Questions

Which is safer, babel-preset-jest or inquirer-search-list?
Based on Nerq's independent trust assessment, babel-preset-jest has a trust score of 48.9/100 (D+) while inquirer-search-list scores 60.0/100 (C). The 11.1-point difference suggests inquirer-search-list has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do babel-preset-jest and inquirer-search-list compare on security?
babel-preset-jest has a security score of N/A/100 and inquirer-search-list scores N/A/100. There is a notable difference in their security assessments. babel-preset-jest's compliance score is 100/100 (EU risk: N/A), while inquirer-search-list's is 100/100 (EU risk: N/A).
Should I use babel-preset-jest or inquirer-search-list?
The choice depends on your requirements. babel-preset-jest (uncategorized, 0 stars) and inquirer-search-list (uncategorized, 0 stars) serve similar use cases. On trust, babel-preset-jest scores 48.9/100 and inquirer-search-list scores 60.0/100. Review the full KYA reports for each agent before making a decision. Consider factors like integration requirements, documentation quality (N/A vs N/A), and maintenance activity (N/A vs N/A).

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.

We use cookies for analytics and caching. Privacy Policy