This page shows every statement about Ferrum with its source, date and limit. The product page is the overview for decision-makers.
How the scale works
- Implemented means the function is present in the source.
- Checked means a named test or a measurement exists.
- Not checked yet means there is no such run yet.
- Not included means the function does not exist, or not in this edition.
The four maturity bands
- Prototype: an early draft, not yet meant for use.
- Early use: the software can be used in a limited setting.
- In use: the software runs in the operation it is meant for.
- Independently reviewed: an independent review exists.
Statements by theme
| Theme | Statement | Status | Date | Version | Source | Limit |
|---|---|---|---|---|---|---|
| Interfaces | In the source code of the full gateway, one gateway exposes seven GA4GH interfaces: DRS, WES, TES, TRS, htsget, Beacon v2 and Crypt4GH. The interfaces are implemented. A full run across every step has not been checked yet. The edge variant does not include three of the seven: WES, TES and TRS. Passports are not one of the seven. The full build includes a Passports route from this program. The edge variant does not include it. With external sign-in, the process logs that Passport checks use ga4gh-infra. | Implemented | 2026-11-15 | 0.3.10 | File in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repository | The interfaces are implemented. A full run across every step has not been checked yet. The edge variant does not include WES, TES, TRS or Passports. The full build includes the Passports route from this program. With external sign-in, the log names ga4gh-infra. Not certified. Details are on the evidence page. Wording in the registryIn the source code of the full gateway, one gateway exposes seven GA4GH interfaces: DRS, WES, TES, TRS, htsget, Beacon v2 and Crypt4GH. The interfaces are implemented. A full run across every step has not been checked yet. The edge variant does not include three of the seven: WES, TES and TRS. Passports are not one of the seven. The full build includes a Passports route from this program. The edge variant does not include it. With external sign-in, the process logs that Passport checks use ga4gh-infra. The interfaces are implemented. A full run across every step has not been checked yet. The edge variant does not include WES, TES, TRS or Passports. The full build includes the Passports route from this program. With external sign-in, the log names ga4gh-infra. Not certified. Details are on the evidence page. |
| Interfaces | Ferrum implements interfaces from the GA4GH standards and is checked with its own tests (HelixTest). | Implemented | 2026-11-15 | 0.3.10 | File in the repositoryFile in the repositoryAsk for the source | No GA4GH certification. First HelixTest runs against other vendors' servers are not comparable and not a certificate. Wording in the registryFerrum implements interfaces from the GA4GH standards and is checked with its own tests (HelixTest). No GA4GH certification. First HelixTest runs against other vendors' servers are not comparable and not a certificate. |
| Interfaces | The edge variant includes DRS, Beacon, htsget and Crypt4GH. Their status requests answer. | Checked | 2026-10-13 | File in the repositoryAsk for the source | WES, TES, TRS and Passports are not part of the edge variant (HTTP 404). HelixTest runs against the edge variant do not pass yet. Wording in the registryThe edge variant includes DRS, Beacon, htsget and Crypt4GH. Their status requests answer. WES, TES, TRS and Passports are not part of the edge variant (HTTP 404). HelixTest runs against the edge variant do not pass yet. | |
| Interfaces | htsget in Ferrum currently returns whole files. Regions (reference name, start, end) are rejected for every kind of data (HTTP 400). | Implemented | 2026-10-20 | 0.3.10 | File in the repositoryFile in the repositoryAsk for the source | A trial showed that the library htsget-search 0.14.0 produces region tickets for BAM and VCF. It is not built in yet. The edge size against the 52,428,800-byte gate is not in the evidence file. Wording in the registryhtsget in Ferrum currently returns whole files. Regions (reference name, start, end) are rejected for every kind of data (HTTP 400). A trial showed that the library htsget-search 0.14.0 produces region tickets for BAM and VCF. It is not built in yet. The edge size against the 52,428,800-byte gate is not in the evidence file. |
| Interfaces | The human Beacon offers part of the standard's routes (status, info, map and variant queries). The framework root paths, answers for individuals and samples, and the three access tiers are missing. | Implemented | 2026-10-21 | 0.3.10 | File in the repositoryFile in the repositoryAsk for the source | Coordinate queries accept only human assemblies and chromosomes. Membership of a Beacon Network was not verified. Wording in the registryThe human Beacon offers part of the standard's routes (status, info, map and variant queries). The framework root paths, answers for individuals and samples, and the three access tiers are missing. Coordinate queries accept only human assemblies and chromosomes. Membership of a Beacon Network was not verified. |
| Interfaces | Known limits: single genomic regions in htsget are rejected, and there is no executor for LSF clusters. | Implemented | 2026-11-15 | 0.3.10 | File in the repositoryFile in the repository | Further limits are listed on the page Evidence and limits. Wording in the registryKnown limits: single genomic regions in htsget are rejected, and there is no executor for LSF clusters. Further limits are listed on the page Evidence and limits. |
| Interfaces | In one local run of the edge variant on 20 October 2026, a SARS-CoV-2 genome file (FASTA, NCBI), a synthetic alignment (BAM) and a synthetic variant file (VCF) were stored and retrieved through DRS. The SHA-256 checksums were equal. Only the genome file was encrypted and decrypted with Crypt4GH. Its SHA-256 checksum was equal. The two synthetic files were not encrypted or decrypted with Crypt4GH. | Checked | 2026-10-20 | 0.3.10 | Ask for the source | The alignment and variant file were synthetic, not a real dataset. Regions through htsget are not possible. This is not a statement about Beacon for pathogen data. Wording in the registryIn one local run of the edge variant on 20 October 2026, a SARS-CoV-2 genome file (FASTA, NCBI), a synthetic alignment (BAM) and a synthetic variant file (VCF) were stored and retrieved through DRS. The SHA-256 checksums were equal. Only the genome file was encrypted and decrypted with Crypt4GH. Its SHA-256 checksum was equal. The two synthetic files were not encrypted or decrypted with Crypt4GH. The alignment and variant file were synthetic, not a real dataset. Regions through htsget are not possible. This is not a statement about Beacon for pathogen data. |
| Interfaces | According to Australian developers (CSIRO), the GA4GH Beacon protocol is focused on human data and has to be adapted for data on pathogens. Adaptations such as PathSBeacon exist. The Public Health Alliance for Genomic Epidemiology (PHA4GE) ran a workshop in 2023 on that. Only Beacon is discussed here. The file-level standards DRS, htsget and Crypt4GH were not assessed here. | Not checked yet | 2026-10-21 | PagePagePage | This entry assesses the Beacon part. The file-level standards DRS, htsget and Crypt4GH were not assessed here. No separate pathogen Beacon is built. The file run of 20 October 2026 is a different entry. Wording in the registryAccording to Australian developers (CSIRO), the GA4GH Beacon protocol is focused on human data and has to be adapted for data on pathogens. Adaptations such as PathSBeacon exist. The Public Health Alliance for Genomic Epidemiology (PHA4GE) ran a workshop in 2023 on that. Only Beacon is discussed here. The file-level standards DRS, htsget and Crypt4GH were not assessed here. This entry assesses the Beacon part. The file-level standards DRS, htsget and Crypt4GH were not assessed here. No separate pathogen Beacon is built. The file run of 20 October 2026 is a different entry. | |
| Access and log | A partner can ask for access to a dataset. For a file bound to a dataset, Ferrum allows access when the sign-in carries a release for that dataset or when the caller is an administrator. Ferrum does not decide the request. | Implemented | 2026-11-07 | main | File in the repositoryFile in the repositoryFile in the repositoryFile in the repository | Present in the code, no end-to-end test. The request exists only when an external decision service is configured. The data holder's decision is not in this program. Unbound files and an administrator account are outside this check. Wording in the registryA partner can ask for access to a dataset. For a file bound to a dataset, Ferrum allows access when the sign-in carries a release for that dataset or when the caller is an administrator. Ferrum does not decide the request. Present in the code, no end-to-end test. The request exists only when an external decision service is configured. The data holder's decision is not in this program. Unbound files and an administrator account are outside this check. |
| Access and log | For a file bound to a dataset, Ferrum allows access when the sign-in carries a release for that dataset or when the caller is an administrator. Access and downloads are recorded. A failed log entry does not stop the request. | Implemented | 2026-11-07 | main | File in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repository | Present in the code, no end-to-end test. The log does not cover every data movement. A failed entry does not stop the request. The data holder's decision is not in this program. Wording in the registryFor a file bound to a dataset, Ferrum allows access when the sign-in carries a release for that dataset or when the caller is an administrator. Access and downloads are recorded. A failed log entry does not stop the request. Present in the code, no end-to-end test. The log does not cover every data movement. A failed entry does not stop the request. The data holder's decision is not in this program. |
| Access and log | Ferrum keeps a hash-chained log of the events it records. | Checked | 2026-10-14 | File in the repositoryAsk for the source | The log covers recorded events only, not every data movement. It does not prove that data stayed on premises. Wording in the registryFerrum keeps a hash-chained log of the events it records. The log covers recorded events only, not every data movement. It does not prove that data stayed on premises. | |
| Access and log | In the program itself, authentication is switched on by default. | Implemented | 2026-10-20 | v0.3.10 | File in the repositoryFile in the repositoryAsk for the source | In the Compose setup shipped for the demo, authentication is off by default (environment variable). Anyone using it beyond a demo switches it on. Wording in the registryIn the program itself, authentication is switched on by default. In the Compose setup shipped for the demo, authentication is off by default (environment variable). Anyone using it beyond a demo switches it on. |
| Access and log | New log rows are appended one after another so that the hash chain does not break under concurrent requests. | Implemented | 2026-10-20 | main | File in the repository | The log covers recorded events only. Not re-tested in this review. Wording in the registryNew log rows are appended one after another so that the hash chain does not break under concurrent requests. The log covers recorded events only. Not re-tested in this review. |
| Where data sits, and the network | When Ferrum runs, the files sit on the storage the operator configures. The default is a directory on the operator's own machine. The source code does not copy those files to a service run by Synaptic Four. | Implemented | 2026-11-07 | main | PageFile in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repository | Present in the code, no end-to-end test. The operator can choose another store, a sync target, or other peers. This does not show that files never leave the premises. Wording in the registryWhen Ferrum runs, the files sit on the storage the operator configures. The default is a directory on the operator's own machine. The source code does not copy those files to a service run by Synaptic Four. Present in the code, no end-to-end test. The operator can choose another store, a sync target, or other peers. This does not show that files never leave the premises. |
| Where data sits, and the network | Ferrum can be operated on your own infrastructure. | Checked | 2026-10-13 | Ask for the source | Not an air gap: the setup includes Postgres, SeaweedFS and Keycloak. Not a clinical deployment. Wording in the registryFerrum can be operated on your own infrastructure. Not an air gap: the setup includes Postgres, SeaweedFS and Keycloak. Not a clinical deployment. | |
| Where data sits, and the network | In two tested setups (edge program on an isolated machine, pinned demo images on an internal network) no outbound connections were observed. Not evidence for every configuration. The time probe (NTP) is intended and could not be sent in the isolated setup. | Checked | 2026-10-20 | Ask for the source | This does not hold for every configuration. The time probe is intended and could not be sent in the isolated setup. Taking in data was not checked, because a sign-in was required. The composed demo setup and the demo start did not run. Only those time windows were observed. Wording in the registryIn two tested setups (edge program on an isolated machine, pinned demo images on an internal network) no outbound connections were observed. Not evidence for every configuration. The time probe (NTP) is intended and could not be sent in the isolated setup. This does not hold for every configuration. The time probe is intended and could not be sent in the isolated setup. Taking in data was not checked, because a sign-in was required. The composed demo setup and the demo start did not run. Only those time windows were observed. | |
| Where data sits, and the network | The health check compares the system clock with a time server, by default pool.ntp.org. The server can be replaced. | Implemented | 2026-10-20 | v0.3.10 | File in the repositoryFile in the repositoryFile in the repositoryFile in the repository | Switching the probe off is not provided for. The probe sends no research data. Wording in the registryThe health check compares the system clock with a time server, by default pool.ntp.org. The server can be replaced. Switching the probe off is not provided for. The probe sends no research data. |
| Where data sits, and the network | It is built so that the data stays on the organisation's own equipment. Not shownA design goal, not evidence. Not shown on the pages until a network test exists. | Not checked yet | Ask for the source | A design goal, not evidence. Not shown on the pages until a network test exists. Wording in the registryIt is built so that the data stays on the organisation's own equipment. A design goal, not evidence. Not shown on the pages until a network test exists. | ||
| Where data sits, and the network | Ferrum has been operated at hosting providers: in a pilot on Fly.io (ended on 13 October 2026) and, since October 2026, on a Contabo server as the public demo. | Checked | 2026-10-20 | 0.3.10 | PageFile in the repositoryAsk for the source | No evidence of duration or load. The pilot has ended. Not one of the large cloud platforms. Wording in the registryFerrum has been operated at hosting providers: in a pilot on Fly.io (ended on 13 October 2026) and, since October 2026, on a Contabo server as the public demo. No evidence of duration or load. The pilot has ended. Not one of the large cloud platforms. |
| Robustness | If the configuration file is invalid, Ferrum does not start instead of continuing with defaults. | Implemented | 2026-10-20 | main | File in the repository | Not re-tested in this review. Wording in the registryIf the configuration file is invalid, Ferrum does not start instead of continuing with defaults. Not re-tested in this review. |
| Robustness | Checkpoint and backup are first written to a temporary file, flushed to disk and then renamed. The aim is that an interruption leaves no half-written file. | Implemented | 2026-10-20 | main | File in the repository | No test with a real power cut. Wording in the registryCheckpoint and backup are first written to a temporary file, flushed to disk and then renamed. The aim is that an interruption leaves no half-written file. No test with a real power cut. |
| Robustness | Goal: Ferrum restarts cleanly after a power cut. The test for this is still outstanding. PlannedAn emergency note is written and is not used at startup. There is no test with a real power cut. | Not checked yet | Ask for the source | An emergency note is written and is not used at startup. There is no test with a real power cut. Wording in the registryGoal: Ferrum restarts cleanly after a power cut. The test for this is still outstanding. An emergency note is written and is not used at startup. There is no test with a real power cut. | ||
| Robustness | An object and its storage reference are written in one database transaction. | Implemented | 2026-10-20 | main | File in the repository | Not re-tested in this review. Wording in the registryAn object and its storage reference are written in one database transaction. Not re-tested in this review. |
| Robustness | Ferrum can tell mains from battery power when monitoring is switched on. So far only mains power was tested, on one Mac. | Checked | 2026-10-14 | File in the repositoryAsk for the source | No detection of an uninterruptible power supply. Monitoring is not on by default on every platform. Wording in the registryFerrum can tell mains from battery power when monitoring is switched on. So far only mains power was tested, on one Mac. No detection of an uninterruptible power supply. Monitoring is not on by default on every platform. | |
| Operation and handover | Runs in Edge mode on a single computer without a database server. Backups can be checked and restored. | Implemented | 2026-11-15 | 0.3.10 | File in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repository | The measurements of the small edition are a separate statement and are not results on small hardware. Creating, checking and restoring a backup was not the recorded step in that check. Wording in the registryRuns in Edge mode on a single computer without a database server. Backups can be checked and restored. The measurements of the small edition are a separate statement and are not results on small hardware. Creating, checking and restoring a backup was not the recorded step in that check. |
| Operation and handover | The edge variant listens by default only on the local address 127.0.0.1. Any other address has to be set explicitly (FERRUM_BIND). | Implemented | 2026-10-20 | main | File in the repositoryFile in the repository | Not re-tested in this review; state 0.3.10 not checked individually. Wording in the registryThe edge variant listens by default only on the local address 127.0.0.1. Any other address has to be set explicitly (FERRUM_BIND). Not re-tested in this review; state 0.3.10 not checked individually. |
| Operation and handover | The edge variant and the full gateway are two builds of the same program (ferrum-gateway) in one source tree. The build decides which interfaces are included. | Implemented | 2026-10-20 | 0.3.10 | File in the repositoryFile in the repositoryFile in the repository | What is not shown is that an operator can move from one size to another without rebuilding. Edge includes DRS, Beacon, htsget and Crypt4GH on SQLite. WES, TES, TRS and Passports belong to the full build. Wording in the registryThe edge variant and the full gateway are two builds of the same program (ferrum-gateway) in one source tree. The build decides which interfaces are included. What is not shown is that an operator can move from one size to another without rebuilding. Edge includes DRS, Beacon, htsget and Crypt4GH on SQLite. WES, TES, TRS and Passports belong to the full build. |
| Operation and handover | The Lab Kit contains an installer for the Raspberry Pi 5. It is written to stop if the data directory is on a microSD card. It has not been run on a real Pi 5. | Implemented | 2026-10-20 | File in the repositoryFile in the repositoryFile in the repository | There is no run yet on a Raspberry Pi, and no measurements. The Lab Kit names 8 GB as the target. Wording in the registryThe Lab Kit contains an installer for the Raspberry Pi 5. It is written to stop if the data directory is on a microSD card. It has not been run on a real Pi 5. There is no run yet on a Raspberry Pi, and no measurements. The Lab Kit names 8 GB as the target. | |
| Operation and handover | A Helm chart for Kubernetes is included. It has not been installed yet. | Implemented | 2026-10-20 | v0.3.10 | File in the repositoryFile in the repository | This is not installed on a cluster. A template ready to run is not shown. Files being present is not a running deployment. Wording in the registryA Helm chart for Kubernetes is included. It has not been installed yet. This is not installed on a cluster. A template ready to run is not shown. Files being present is not a running deployment. |
| Operation and handover | The source tree includes an installation guide and an operator handbook. They describe how to set Ferrum up without Synaptic Four. They do not state support terms. | Implemented | 2026-11-07 | main | File in the repositoryFile in the repositoryFile in the repositoryFile in the repositoryFile in the repository | Present in the source tree, not installed in this review. No support promise, and no promise that Synaptic Four runs the system. Wording in the registryThe source tree includes an installation guide and an operator handbook. They describe how to set Ferrum up without Synaptic Four. They do not state support terms. Present in the source tree, not installed in this review. No support promise, and no promise that Synaptic Four runs the system. |
| Operation and handover | The path from the README to the first query took about 25 minutes once, including building the images. | Checked | 2026-10-13 | Ask for the source | A single measurement. The duration depends on machine, network and cache. Wording in the registryThe path from the README to the first query took about 25 minutes once, including building the images. A single measurement. The duration depends on machine, network and cache. | |
| Operation and handover | The public demo requires a login for Ferrum. The demo credentials are shown openly on the suite page of the demo on purpose. | Implemented | 2026-10-20 | 0.3.10 | PageFile in the repository | Nobody logged in for this note. Which accounts work was not checked. Please do not enter real personal data. Wording in the registryThe public demo requires a login for Ferrum. The demo credentials are shown openly on the suite page of the demo on purpose. Nobody logged in for this note. Which accounts work was not checked. Please do not enter real personal data. |
| Operation and handover | Ferrum stores Nanopore raw files (POD5, FAST5, BLOW5) and quality metrics supplied by the caller. | Checked | 2026-10-14 | File in the repositoryAsk for the source | Ferrum does not read these files itself and computes no metrics from them. Wording in the registryFerrum stores Nanopore raw files (POD5, FAST5, BLOW5) and quality metrics supplied by the caller. Ferrum does not read these files itself and computes no metrics from them. | |
| Operation and handover | The edge variant starts in about 27 milliseconds and uses about 17 MB of memory when idle. | Checked | 2026-10-13 | Ask for the source | No statement about small hardware such as the Raspberry Pi. The state is older than the current version. Wording in the registryThe edge variant starts in about 27 milliseconds and uses about 17 MB of memory when idle. No statement about small hardware such as the Raspberry Pi. The state is older than the current version. | |
| Operation and handover | Maturity: Early use. | Not checked yet | 2026-11-14 | File in the repository | No review by a third party. HelixTest checks are not GA4GH certification. A published revision and the current branch are not the same revision. Wording in the registryMaturity: Early use. No review by a third party. HelixTest checks are not GA4GH certification. A published revision and the current branch are not the same revision. | |
| Licence | Ferrum is under the Apache licence 2.0. You may use it, change it and pass it on freely, including commercially. | Implemented | 2026-11-14 | File in the repository | Not legal advice. The text of the licence file is what counts. Wording in the registryFerrum is under the Apache licence 2.0. You may use it, change it and pass it on freely, including commercially. Not legal advice. The text of the licence file is what counts. | |
| Versions and tests | Ferrum's own checks (formatting, lint, 282 tests, licence check) passed on 13 October 2026 at commit with Rust 1.91.1. | Checked | 2026-10-13 | v0.3.6 | File in the repositoryAsk for the source | An older state than v0.3.10. Not an independent run. Tests show only what they cover. Wording in the registryFerrum's own checks (formatting, lint, 282 tests, licence check) passed on 13 October 2026 at commit with Rust 1.91.1. An older state than v0.3.10. Not an independent run. Tests show only what they cover. |
| Versions and tests | Ferrum pins the Rust version (1.91.1). The build containers use the same version with a pinned checksum. | Implemented | 2026-10-20 | 0.3.10 | File in the repository | Whether the images can be rebuilt with this toolchain is not shown. Wording in the registryFerrum pins the Rust version (1.91.1). The build containers use the same version with a pinned checksum. Whether the images can be rebuilt with this toolchain is not shown. |
| Versions and tests | A change log lists every version. Behaviour changes are listed separately, for example in version 0.3.7 of 17 October 2026. | Implemented | 2026-10-17 | 0.3.7 | File in the repository | The change log is not a test that each named behaviour still holds in 0.3.10. Wording in the registryA change log lists every version. Behaviour changes are listed separately, for example in version 0.3.7 of 17 October 2026. The change log is not a test that each named behaviour still holds in 0.3.10. |
| Versions and tests | Ferrum versions from v0.1.0 to v0.3.10 are published as tags. The public demo reported version 0.3.10 on 20 October 2026. | Implemented | 2026-10-20 | 0.3.10 | PageFile in the repositoryFile in the repository | Whether the images match the public store bit for bit is not shown. Wording in the registryFerrum versions from v0.1.0 to v0.3.10 are published as tags. The public demo reported version 0.3.10 on 20 October 2026. Whether the images match the public store bit for bit is not shown. |
| Versions and tests | Building four of the five programs that were checked gave identical checksums in two clean runs on the same platform. | Checked | 2026-10-11 | Ask for the source | Not checked across platforms and not in continuous integration. The HelixTest release binaries did not match. Wording in the registryBuilding four of the five programs that were checked gave identical checksums in two clean runs on the same platform. Not checked across platforms and not in continuous integration. The HelixTest release binaries did not match. | |
| Versions and tests | Ferrum is written in Rust. Its own code (about 54,000 lines in 244 files) contains four unsafe sites in three files. | Implemented | 2026-10-20 | v0.3.10 | File in the repositoryFile in the repositoryFile in the repositoryFile in the repository | Encryption uses the C library libsodium through sodiumoxide (in third_party/crypt4gh, not counted here). Rust rules out memory errors in Synaptic Four's own code where no unsafe is involved, and says nothing else about security. Wording in the registryFerrum is written in Rust. Its own code (about 54,000 lines in 244 files) contains four unsafe sites in three files. Encryption uses the C library libsodium through sodiumoxide (in third_party/crypt4gh, not counted here). Rust rules out memory errors in Synaptic Four's own code where no unsafe is involved, and says nothing else about security. |
What will be checked next (As of: 19 November 2026)
-
Goal: a restart after a power cut. The test for this is still outstanding.
Planned
An emergency note is written and is not used at startup. There is no test with a real power cut.
-
It is built so that no data leaves the organisation (see above).
Not shown
A design goal, not evidence. Not shown on the pages until a network test exists.
-
A run of the Pi installer on a Raspberry Pi, and measurements on a Pi.
-
Sign-in of the demo users (the run did not sign in).
-
Analysis of Nanopore raw files.
Tested
Ferrum does not read these files itself and computes no metrics from them.
-
A complete log of every data movement.
Tested
The log covers recorded events only, not every data movement. It does not prove that data stayed on premises.
-
Conformity of the edge variant: the HelixTest runs do not complete yet.
Tested
WES, TES, TRS and Passports are not part of the edge variant (HTTP 404). HelixTest runs against the edge variant do not pass yet.
-
Operation on one of the large cloud platforms, and a test of the Helm chart on a cluster.
-
Certification or an independent security review: none.
Present in the code
No GA4GH certification. First HelixTest runs against other vendors' servers are not comparable and not a certificate.
-
In the source code of the full gateway, one gateway exposes seven GA4GH interfaces: DRS, WES, TES, TRS, htsget, Beacon v2 and Crypt4GH. Code that exists is not an end-to-end test. The edge variant does not include three of the seven: WES, TES and TRS. Passports are not one of the seven. The full build includes a Passports route from this program. The edge variant does not include it. With external sign-in, the process logs that Passport checks use ga4gh-infra.
Present in the code
Code that exists is not an end-to-end test. The edge variant does not include WES, TES, TRS or Passports. The full build includes the Passports route from this program. With external sign-in, the log names ga4gh-infra. Not certified. Details are on the evidence page.
Next step in the registry
Cite a CI or recorded local stack run before TESTED.
-
It is built so that the data stays on the organisation's own equipment.
Not shown
A design goal, not evidence. Not shown on the pages until a network test exists.
Next step in the registry
Cite before any evidence level. This entry does not use that run as proof.
Interfaces and versions
A table of all endpoints per interface (specification, version, scope) is in progress.