Rohithgilla12/data-peek - Open Source PR Review Scorecard

A minimal, fast, database client desktop application. Built for developers who want to quickly peek at their data without the bloat.

C-Rank Grade: D (Risky) - 30/100

External PR Merge Rate: -

Response Time: <1h

First Timer Success: -

Frequently Asked Questions

Is Rohithgilla12/data-peek welcoming to first-time open-source contributors?

Rohithgilla12/data-peek has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in Rohithgilla12/data-peek respond to incoming external pull requests in approximately 0.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 29.9 C-Rank™ score (D Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 29.9 places Rohithgilla12/data-peek in the D tier.

What is the external contributor pull request merge rate for Rohithgilla12/data-peek?

The external contributor pull request merge rate for Rohithgilla12/data-peek is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Rohithgilla12/data-peek?

Rohithgilla12/data-peek currently has 13 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

Rohithgilla12
Rohithgilla12/data-peekD•Risky1.7k
GitHub
Back to Explorer
Rohithgilla12

Rohithgilla12/data-peek

1,678
InactiveD•Risky(30/100)Low Sample (<20 PRs)TypeScript

A minimal, fast, database client desktop application. Built for developers who want to quickly peek at their data without the bloat.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in Rohithgilla12/data-peek welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe29/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for Rohithgilla12/data-peek
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/Rohithgilla12/data-peek)](https://getmerged.abhishekco.de/Rohithgilla12/data-peek?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

What The Format SQL menu item (Shift+Alt+F, apps/desktop/src/main/menu.ts:211) sends menu:format-sql to the renderer, and the preload exposes window.api.menu.onFormatSql, but nothing in apps/desktop/src/renderer/src subscribes to it. Choosing it from the menu, or pressing Shift+Alt+F, does nothing. The working shortcut is Monaco's own Cmd/Ctrl+Shift+F command in sql-editor.tsx. This came up in #283, which dropped Shift+Alt+F from the docs for this reason. These preload menu listeners also have no renderer subscriber, so their menu items may be no-ops when clicked. Their keyboard shortcuts may still work through renderer hotkeys, so please verify each one: onNewTab (menu:new-tab) onCloseTab (menu:close-tab) onExecuteQuery (menu:execute-query) onClearResults (menu:clear-results) How Subscribe to onFormatSql where the active SQL editor lives, and run the same format action as the Monaco Cmd/Ctrl+Shift+F command. Return the cleanup function from useEffect, like the existing onToggleWatc

📅 Opened Oct 2, 2026💬 1 comment
Quality: 90/100Contribute

What Follow-up to #278 / #284. Seeded data-generator runs are now reproducible for nulls, enums, and FK picks, but random-date still isn't. When a column has no minValue/maxValue, generateValue in apps/desktop/src/main/data-generator.ts builds its window from Date.now(): case 'random-date': { const from = new Date(col.minValue ?? Date.now() - 365 * 24 * 60 * 60 * 1000) const to = new Date(col.maxValue ?? Date.now()) return faker.date.between({ from, to }).toISOString() } The renderer heuristic (apps/desktop/src/renderer/src/lib/data-gen-heuristics.ts) emits a bare { generatorType: 'random-date' } for most date/timestamp columns, so this is the common path. Two runs with the same seed produce slightly different dates. How When config.seed is set, anchor the default window to a fixed reference instead of Date.now(). For example, capture now once at the start of generateRows, and use a fixed epoch when seeded (or faker's refDate). Unseeded runs should keep today's behaviour: the la

📅 Opened Oct 2, 2026💬 2 comments
Quality: 90/100Contribute

What batchInsert in apps/desktop/src/main/batch-insert.ts binds every cell as a parameter. The default batch size is 500 rows (apps/desktop/src/main/ipc/import-handlers.ts, apps/desktop/src/renderer/src/stores/data-gen-store.ts) and the CSV import dialog allows up to 5,000. SQL Server caps a statement at 2,100 parameters, so a 500-row import of a 5-column table fails. SQL Server also caps a VALUES list at 1,000 rows. Postgres caps parameters at 65,535 (5,000 rows × 14 columns). How Add a pure effectiveBatchSize(dialect, columnCount, requested) in batch-insert.ts that clamps to the dialect's parameter and row limits, and use it to split batches. Export buildInsertSql and buildPlaceholders so they can be tested directly. Add apps/desktop/src/main/__tests__/batch-insert.test.ts covering the clamp for each dialect and the placeholder numbering across split batches. Out of scope MSSQL onConflict: 'skip' | 'update' is currently a plain INSERT; that needs MERGE and its own issue. Done wh

📅 Opened Oct 1, 2026💬 1 comment
Quality: 90/100Contribute

What Schema Intel is in the sidebar (apps/desktop/src/renderer/src/components/app-sidebar.tsx) and now also powers npx data-peek doctor, but there is no feature page under apps/docs/content/docs/features/ and no README entry. How Write apps/docs/content/docs/features/schema-intel.mdx from SCHEMA_INTEL_CHECKS in packages/shared/src/index.ts: what each check finds, its severity, and a per-database support matrix (Postgres, MySQL, SQL Server, SQLite) from supportedDbTypes. Explain the Run Fix flow and that suggested SQL is a starting point, not a blind apply. Link to the CLI reference page at apps/docs/content/docs/reference/cli.mdx for the terminal version. Register the page in apps/docs/content/docs/features/meta.json and add a bullet to the Features section in README.md. Match the tone of features/health-monitor.mdx: what it is, when you reach for it, then the details. Done when pnpm --filter docs build passes and the page is in the sidebar. Difficulty: easy. Docs only.

📅 Opened Oct 1, 2026💬 2 comments
Quality: 100/100Contribute

What Three places where the docs and the code disagree. README.md says "Export results to CSV, JSON, or Excel". There is no Excel export. The header comment in apps/desktop/src/renderer/src/lib/export.ts and a stray 'xlsx' member in ExportOptions in the same file are leftovers. Fix the README and remove the dead type member. apps/docs/content/docs/features/health-monitor.mdx says Health Monitor is PostgreSQL-only. The MySQL and SQL Server adapters implement getActiveQueries, getTableSizes, getCacheStats, and getLocks. Verify each panel against a live MySQL and SQL Server connection, then update the support note to say exactly what works where. apps/docs/content/docs/database-support/index.mdx marks SQL Server custom types as unsupported, but getTypes in apps/desktop/src/main/adapters/mssql-adapter.ts returns user-defined types. Update the matrix. Done when All three statements match the code, with a line in the PR saying how each was verified. Difficulty: easy. Docs plus one dead-c

📅 Opened Oct 1, 2026💬 1 comment
Quality: 100/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for Rohithgilla12/data-peek

When evaluating whether to contribute to Rohithgilla12/data-peek, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of Rohithgilla12/data-peek acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to Rohithgilla12/data-peek

01

Is Rohithgilla12/data-peek welcoming to first-time open-source contributors?

Rohithgilla12/data-peek has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 29.9 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 29.9 places Rohithgilla12/data-peek in the Risky tier.

04

What is the external contributor pull request merge rate for Rohithgilla12/data-peek?

The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in Rohithgilla12/data-peek?

Yes, Rohithgilla12/data-peek currently has 13 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for Rohithgilla12/data-peek are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.