Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-08 15:42 UTC

evangelosmeklis / peepdb

CLI tool and python library to inspect databases fast.

PythonGPL-3.0★ 494 stars⑂ 20 forkssince Aug 2024View on GitHub ↗
KindCommand-line toolhow this is determined

evangelosmeklis/peepdb holds a health index of 28 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (69/100) and lowest on Vitality (28/100). It was last updated 461 days ago. A single contributor accounts for most of its recent work.

28
overall / 100
At Risk

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

28
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 48 is calibrated to 47 on the published index scale (record calibration 2026-08-02).

Ownership

Evangelos MeklisPersonal account
38 followers18 public repossince Nov 2019Nokia

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIpeepdbpoints to another repo — not scored0.1.4513710 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

28At Risk · 21% of overall
How it's scored
0/36Push recencylast push 461 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push461
active_weeks_last_year0
How it's scored
27/27Ships releases4 releases published
7.2/36Release recencylatest release 710 days ago
27/27Release cadencea release every ~7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count4
latest_release_tagv0.1.4
releases_from_tagsno
days_since_latest_release710
mean_days_between_releases7
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

64Moderate · 17% of overall
How it's scored
43.7/60Stars494 stars
10.7/25Forks20 forks
4.7/15Watchers8 watchers
Inputs used
forks20
stars494
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

49Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.2/22.5Commit distributiontop contributor authored 86% of commits
9.5/13.5Contributor breadth7 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.857
How it's scored
31/42Issue resolution74% of issues closed
25.2/30PR acceptance26/31 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 10/29 approved changesets -- score normalized to 3
Inputs used
merged_prs26
open_issues10
closed_issues28
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.737
closed_unmerged_prs5
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.4/25Owner reach38 followers of evangelosmeklis
21.3/25Track record18 public repos, account ~6 yr old
Inputs used
followers38
owner_typeUser
is_verified
owner_loginevangelosmeklis
public_repos18
account_age_days2,497
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 18 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.peepdb.dev/
10/10Repository description
10/10Topics12 topics
10/10Wiki
Inputs used
topicsdatabase-management, python3, sql, cli, python, open-source, backend-as-a-service, database-as-a-service, developer-tools, nosql, serverless, daatabase
has_wikiyes
homepagehttps://docs.peepdb.dev/
docs_sitehttps://docs.peepdb.dev/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

35Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 18 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 10/29 approved changesets -- score normalized to 3
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities46 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
7.6/35Direct dependencies free of known advisories1 affected: mariadb 1.1.14 (critical 9.8)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages20
unassessed_packages0
affected_by_severitycritical 1
direct_affected_packages1
Matched the pypi:peepdb@0.1.4 runtime dependency closure — what installing the published package pulls in — 20 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

31At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18/40Legible commit history26 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.338
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 77
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/24 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes7,565
source_files_sampled24
oversized_source_files0

Key facts

494GitHub stars
7contributors
0commits, last 12 months
461days since last push
4releases
1bus factor
10open issues
PyPI, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi package 'peepdb' points at a different repository (https://github.com/PeepDB-dev/peepdb); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 20 ⇿
0Stars
20Forks
2Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0481216202032024-092025-052026-01
Major 0Minor 0Patch 2

Each point covers 2 days.

OpenSSF Scorecard 2.6 / 10
2.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-08 15:41 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 18 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/29 approved changesets -- score normalized to 3
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities46 existing vulnerabilities detected
All dependencies 107

Full resolved dependency set from the GitHub dependency graph: 0 direct and 107 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIasync-timeout4.0.3indirect
PyPIbackports-tarfile1.2.0indirect
PyPIcachecontrol0.14.0indirect
PyPIcachetoolsindirect
PyPIcachetools5.5.0indirect
PyPIcertifi2024.8.30indirect
PyPIcffi1.17.1indirect
PyPIcharset-normalizer3.3.2indirect
PyPIclickindirect
PyPIclick8.1.7indirect
PyPIcoverage7.6.1indirect
PyPIcryptographyindirect
PyPIcryptography43.0.0indirect
PyPIdnspython2.6.1indirect
PyPIexceptiongroup1.2.2indirect
PyPIfirebase-admin6.5.0indirect
PyPIgoogle-api-core2.20.0indirect
PyPIgoogle-api-python-client2.147.0indirect
PyPIgoogle-auth2.35.0indirect
PyPIgoogle-auth-httplib20.2.0indirect
PyPIgoogle-cloud-core2.4.1indirect
PyPIgoogle-cloud-firestore2.19.0indirect
PyPIgoogle-cloud-storage2.18.2indirect
PyPIgoogle-crc32c1.6.0indirect
PyPIgoogle-resumable-media2.7.2indirect
PyPIgoogleapis-common-protos1.65.0indirect
PyPIgrpcio1.66.2indirect
PyPIgrpcio-status1.66.2indirect
PyPIhttplib20.22.0indirect
PyPIidna3.10indirect
PyPIimportlib-metadata8.5.0indirect
PyPIiniconfig2.0.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.0.1indirect
PyPIjaraco-functools4.1.0indirect
PyPIkeyringindirect
PyPIkeyring25.4.1indirect
PyPImariadbindirect
PyPImariadb1.1.10indirect
PyPImore-itertools10.5.0indirect
PyPImsgpack1.1.0indirect
PyPImysql-connector-pythonindirect
PyPImysql-connector-python9.0.0indirect
PyPIoracledb2.5.1indirect
PyPIpackaging24.1indirect
PyPIpluggy1.5.0indirect
PyPIproto-plus1.24.0indirect
PyPIprotobuf5.28.2indirect
PyPIpsycopg2-binaryindirect
PyPIpsycopg2-binary2.9.9indirect
PyPIpyasn10.6.1indirect
PyPIpyasn1-modules0.4.1indirect
PyPIpycparser2.22indirect
PyPIpyjwt2.9.0indirect
PyPIpymongo4.9.1indirect
PyPIpymysqlindirect
PyPIpymysql1.1.1indirect
PyPIpyodbc5.2.0indirect
PyPIpyparsing3.1.4indirect
PyPIpytest8.3.2indirect
PyPIpytest-cov5.0.0indirect
PyPIredis5.2.0indirect
PyPIrequests2.32.3indirect
PyPIrsa4.9indirect
PyPItabulateindirect
PyPItabulate0.8.9indirect
PyPItomli2.0.1indirect
PyPIuritemplate4.1.1indirect
PyPIurllib32.2.3indirect
PyPIzipp3.20.2indirect
RubyGemsaddressable2.8.7indirect
RubyGemsbigdecimal3.1.8indirect
RubyGemscolorator1.1.0indirect
RubyGemsconcurrent-ruby1.3.4indirect
RubyGemsem-websocket0.5.3indirect
RubyGemseventmachine1.2.7indirect
RubyGemsffi1.17.0indirect
RubyGemsffi1.17.0-x86_64-linux-gnuindirect
RubyGemsforwardable-extended2.6.0indirect
RubyGemsgoogle-protobuf4.27.3indirect
RubyGemshttp_parser.rb0.8.0indirect
RubyGemsi18n1.14.5indirect
RubyGemsjekyll4.3.3indirect
RubyGemsjekyll-include-cache0.2.1indirect
RubyGemsjekyll-sass-converter3.0.0indirect
RubyGemsjekyll-seo-tag2.8.0indirect
RubyGemsjekyll-watch2.2.1indirect
RubyGemsjust-the-docs0.9.0indirect
RubyGemskramdown2.4.0indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemsliquid4.0.4indirect
RubyGemslisten3.9.0indirect
RubyGemsmercenary0.4.0indirect
RubyGemspathutil0.16.2indirect
RubyGemspublic_suffix6.0.1indirect
RubyGemsrake13.2.1indirect
RubyGemsrb-fsevent0.11.2indirect
RubyGemsrb-inotify0.11.1indirect
RubyGemsrexml3.3.5indirect
RubyGemsrouge4.3.0indirect
RubyGemssafe_yaml1.0.5indirect
RubyGemssass-embedded1.77.8indirect
RubyGemssass-embedded1.77.8-x86_64-linux-gnuindirect
RubyGemsstrscan3.1.0indirect
RubyGemsterminal-table3.0.2indirect
RubyGemsunicode-display_width2.5.0indirect
RubyGemswebrick1.8.1indirect
Dependency advisories 1

Installing pypi:peepdb@0.1.4 pulls in 20 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
mariadb1.1.14directcritical1

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.