authorizer

Your data, your control. Fully open source, authentication and authorization. No lock-ins. Deployment in Railway in 120 seconds || Spin a docker image as a micro-service in your infra. Built in login page and Admin panel out of the box.

Runssource: GitHubhomepageGoApache-2.0commit 891f58fdd82b

Go, Apache-2.0 licensed. The project labels itself: 2fa, auth, authentication, authorization, docker, golang, graphdb and graphql.

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

Authorizer server builds, passes go vet, runs 42 test suites successfully (all SQLite-compatible tests), and serves HTTP (port 8080), gRPC (port 9091), and metrics (port 8081), health and GraphQL endpoints respond correctly.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
2,125
forks
225
open issues
74
watchers
15
size
18 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 authorizer, 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.

  • Missing external database containers (PostgreSQL, MongoDB, ArangoDB, ScyllaDB, DynamoDB, Couchbase) for integration tests6 minutes
  • MongoDB-specific index tests skipped (connection refused on localhost:27017)
Install time
18 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go build ./... && go vet ./... exited 0; go test ./...: 42 packages passed (ok), health endpoint returned 200 with {'status':'ok'}, readyz returned 200 with {'status':'ready'}, GraphQL schema introspection returned 200 with valid response
Model tokens used
170,002
Exact commit tested
891f58fdd82b
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.

FAIL
FAIL  github.com/authorizerdev/authorizer/internal/storage/db/mongodb  120.008s
FAIL
=== Server binary ===
/bin/sh: 18: file: not found
Now I have all the data. Let me compile the report.
exec
/bin/sh -lc "ls -la /tmp/authorizer 2>/dev/null | awk '{print "'$5, $NF}'"'" in /work/repo
 succeeded in 0ms:
117805040 /tmp/authorizer
tokens used
170,002

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 2 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 18 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 2fa projects Argusic has installed and timed, authorizer was the 4th fastest to reach a running state, and 2 of 4 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.10
Argusic Runner1/3Runs100.000.12

Topics (from GitHub)

2faauthauthenticationauthorizationdockergolanggraphdbgraphqlhacktoberfestmagic-linkmicroservicenosqloauth2role-based-access-controlsecuritysocial-loginssqltypescriptuser-privileges

Embed the badge

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

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

Questions

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