syncope

Apache Syncope

Runssource: GitHubhomepageJavaApache-2.0commit ff7de522d3c5

Java, Apache-2.0 licensed. The project labels itself: access management, api gateway, api management, authentication, authorization, enforce policies, identity governance and identity management.

syncope runs. An Argusic agent installed it in 23 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Apache Syncope compiles and all 602 unit tests pass on JDK 25 with Maven 3.9.9, no errors or failures.

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.07 (measured)
recorded runs
1
last tested
stars
349
forks
211
open issues
1
watchers
25
size
91 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.

Install time
23 minutes
Cold machine to finish
24 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
mvn test -pl core/idm/logic -am ran 602 tests across 10 modules (common/idrepo/lib, common/am/lib, core/persistence/api, core/provisioning/api, core/spring, core/persistence/jpa, core/workflow/java, core/provisioning/java, core/idrepo/logic, core/idm/logic) plus additional standalone runs on client/idrepo/lib (2 tests) and common/keymaster/client-zookeeper (6 tests); all tests passed, BUILD SUCCESS
Model tokens used
172,752
Exact commit tested
ff7de522d3c5
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.

 succeeded in 0ms:
[INFO] BUILD SUCCESS
exec
/bin/sh -lc 'cat /tmp/test_output.txt | grep "Total time:"' in /work/repo
 succeeded in 0ms:
[INFO] Total time:  03:33 min
All done. Here's the complete report.
The full-project compile (`mvn compile -q`) succeeded. 602 tests across all modules passed with 0 f…
tokens used
172,752
All done. Here's the complete report.
The full-project compile (`mvn compile -q`) succeeded. 602 tests across all modules passed with 0 f…

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.
  • Installed in 23 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner1/3Runs100.000.07

Topics (from GitHub)

access-managementapi-gatewayapi-managementauthenticationauthorizationenforce-policiesidentity-governanceidentity-managementidentity-provideridentity-provisioningmicroservicesoauth2openidconnectproxyrequest-routingsaml2scimsecurityservice-meshsso

Embed the badge

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

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

Questions

Does syncope run?
Yes. syncope runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test syncope?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ff7de522d3c5. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test syncope?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does syncope take to install?
23 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 syncope need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing syncope?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for syncope?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion