Suggest adding: Entity Ledger — free Cyprus company search with risk signals (English)

Open Beginner friendly
#131 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet

Research direction

Find the Cyprus/company-records section in the collection and review how similar resources are listed. Add the Entity Ledger Cyprus link with a concise description of its English-language search and risk signals, while preserving the stated ownership-data limitation; done means the resource appears accurately in the relevant list.

Written by the indexing model from the issue text.

Description

Hi — suggesting a free resource for the Cyprus / company-records section.

Entity Ledger — Cyprushttps://entityledger.io/cyprus

Free, English-language search of 508k+ Cyprus companies with computed risk signals: court liquidations (~66k), Cyprus Gazette insolvency notices (~64k documents), strike-off pending, offshore-leak appearances, and Central-Bank-of-Cyprus regulated/authorised status (payment & e-money institutions). It also tracks changes for monitoring.

Why it is useful: the official Cyprus registry is €10-per-search, Greek-heavy, and exposes no risk signals or ownership graph. Entity Ledger is a free first pass for company existence, directors/secretaries, status, distress signals, and regulated status — all in English.

Honest limitation: it does not expose full shareholder / UBO data for free (Cyprus suspended public UBO access in 2022; full shareholders still require the paid HE32 filing). So it complements, not replaces, paid ownership lookups.

No affiliation requirement — sharing as a genuinely useful free Cyprus resource. Thanks for maintaining this list.

Dominant language
HTML
Stars
8.8k
Forks
1k
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cipher387/osint_stuff_tool_collection

All issues in cipher387/osint_stuff_tool_collection

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.