apinto

基于golang开发的网关。具有各种插件,可以自行扩展,即插即用。此外,它可以快速帮助企业管理API服务,提高API服务的稳定性和安全性。

Runssource: GitHubhomepageGoApache-2.0commit 708a2ec565a0

Go, Apache-2.0 licensed. The project labels itself: api, api gateway, apigateway, apinto, dubbo2, gateway, go and goku.

apinto runs. An Argusic agent installed it in 13 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Apinto API gateway builds from source, the binary reports its version, and the gateway process starts listening on the admin API (port 9400, HTTP 200) and the proxy port (8099, HTTP 404).

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 91.4 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
91.4 / 100
cost of the verifying run
$0.31 (measured)
recorded runs
2
last tested
stars
1,684
forks
259
open issues
47
watchers
31
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.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing apinto, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Go compiler not installed in environment2 minutes
  • router/http-router/append_test.go: undefined CheckJson2 minutes
  • utils/json_test.go: non-constant format string in t.Logf1 minute
  • go build ./... failed with missing go.sum entries0.4 minutes
Install time
13 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
curl http://127.0.0.1:9400/ returned HTTP 200 with {"status":404,"header":null,"data":null}; curl http://127.0.0.1:8099/ returned HTTP 404 (expected with no routes); go build ./... exits 0; selected package tests pass
Model tokens used
211,021
Exact commit tested
708a2ec565a0
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Now filling in the mandatory JSON:
**Errors encountered:**
1. No Go installed - downloaded Go 1.22.10 tarball (fixed, ~2 min)
2. `go build ./...` - missing go.sum entries - `go mod tidy` (fixed, ~25s)
3. `router/http-router/append_test.go` - undefined `CheckJson` (fixed with sed/test rewrite, ~2 min)
4. `utils/json_test.go` - non-constant format string (fixed with sed, ~1 min)
**Verification:**
- `curl http://127.0.0.1:9400/` returned `{"status":404,"header":null,"data":null}` (HTTP 200)
- `curl http://127.0.0.1:8099/` returned 404 (expected, no routes configured)
- `./apinto version` printed version info (though "unknown" for build metadata)
- `go build ./...` exits 0 - all packages compile
- `go test ./checker/...` passed, `go test ./router/http-router/...` passed (with fix), `go test ./…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 13 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.

Of the 62 api projects Argusic has installed and timed, apinto was the 50th fastest to reach a running state, and 37 of 62 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.31
Argusic Runner1/3Runs82.860.10

Topics (from GitHub)

apiapi-gatewayapigatewayapintodubbo2gatewaygogokugolanggrpcloadbalancermicroservicemiddlewarepluginproxyrouterservicemesh

Embed the badge

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

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

Questions

Does apinto run?
Yes. apinto runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test apinto?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 708a2ec565a0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test apinto?
The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does apinto take to install?
13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does apinto need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing apinto?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does apinto compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, apinto was the 50th fastest to reach a running state, and 37 of 62 reached one at all.
Where is the evidence for apinto?
All 2 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