reactivesearch-api

API Gateway for Elasticsearch with declarative querying and out-of-the-box access controls

Not yet testedsource: GitHubhomepageGoApache-2.0commit 8d9acac8b4c0

Go, Apache-2.0 licensed. The project labels itself: api gateway, elasticsearch, elasticsearch api, elasticsearch plugin, hacktoberfest and reactivesearch.

reactivesearch-api has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
212
forks
30
open issues
11
watchers
9
size
6 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

  • dejavu tested, not verified · JavaScript · 2 shared topics

Run history

No recorded runs.

Topics (from GitHub)

api-gatewayelasticsearchelasticsearch-apielasticsearch-pluginhacktoberfestreactivesearch

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/reactivesearch-api.svg)](https://argusic.com/subject/reactivesearch-api)

Questions

Does reactivesearch-api run?
reactivesearch-api has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test reactivesearch-api?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for reactivesearch-api?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion