# yint-tech/sekiro-open

SEKIRO is a multi-language, distributed, network topology-independent service publishing platform. By writing handlers in their respective languages, functionalities can be published to the central API marketplace. Business systems utilize the capabilities of remote nodes through RPC.

Repository: https://github.com/yint-tech/sekiro-open
Canonical: https://ross.abutalabs.com/products/sekiro-open
Homepage: https://sekiro.iinti.cn/sekiro-doc/
Language: Java
License Family: other
Topics: js-rpc, rpc, webrpc
Last push: 2026-08-20T13:56:57+00:00

## Health v2 (maintenance only)
Score: 67/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 98, release rhythm 8, longevity 100
- inputs: {"age_days": 2521, "days_push": 13, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1912, forks 537 (observed 2026-08-28T04:05:53.395661+00:00)

## What it is
Sekiro is a multi-language, distributed service publishing platform that lets handlers written in various languages register with a central server and expose their capabilities as RPC APIs. It specializes in exposing functionality from restricted environments (mobile apps, browsers, intranets) to external business systems over reverse connections.

## Use cases
- expose encryption algorithms from a mobile app as an API without reverse engineering them
- call intranet-only services from external systems via an in-network client
- proxy B-end business requests through app/terminal devices (RPC crawling)
- publish services without revealing provider IP or source code
- manage distributed API endpoints with auth, load balancing, and quota control

## When to choose
- you need to call code running in restricted contexts like Android apps, Frida/Xposed hooks, or browsers
- your nodes sit behind NAT or firewalls and cannot expose ports
- you want a self-hosted API gateway for cross-language remote handlers

## When to avoid
- you need conventional datacenter-to-datacenter microservices RPC where gRPC, Dubbo, or Spring Cloud fit better
- you require an OSI-approved open-source license for commercial use
- you need a lightweight in-process RPC library rather than a hosted platform

## Facets
- artifact type: service
- maturity: active
- function: rpc, api-framework, middleware, auth, monitoring
- domain: apis, microservices, backend, developer-tools
- platform: jvm, self-hosted, cross-platform
- tags: rpc-framework, service-publishing, api-marketplace, reverse-connect, frida, xposed, crawler-rpc, multi-language, nat-traversal, automation, docker, linux

## Member repositories
- yint-tech/sekiro-open (main) score 67

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:53.395661+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:10:39.883913+00:00, confidence not recorded.
  - readme: https://github.com/yint-tech/sekiro-open (fetched 2026-08-28T04:05:53.395661+00:00, sha 92d1bfc940dc)
  - homepage: https://sekiro.iinti.cn/sekiro-doc/ (fetched 2026-08-29T10:50:02.575811+00:00, sha 83b7e308714b)
  - site_page: https://sekiro.iinti.cn/sekiro-doc/01_manual/1.quickstart.html (fetched 2026-08-29T10:50:02.644394+00:00, sha bc0a4302f745)
  - site_page: https://sekiro.iinti.cn/sekiro-doc/01_manual/4.server_install.html (fetched 2026-08-29T10:50:02.669143+00:00, sha abe3cfc2243f)
- Data as of 2026-08-30T08:39:29.467469+00:00.