SP1 Helios has 2 public audit reports from Zellic; the latest is Zellic, 29 Jul 2025; 1 critical finding, 1 acknowledged, not fixed.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
1 finding is still open or acknowledged in the firms’ reports: 1 critical.
No test suite is in place
SP1 Helios · Zellic · 29 Jul 2025 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| SP1 Helios | Security firm: Zellic | Date: | Scope: —Not recorded; see the report | 1 critical acknowledged, not fixed | Findings: 1 critical · 1 medium 1 fixed · 1 acknowledged | GitHub ↗ |
| OP Succinct | Security firm: Zellic | Date: | Scope: —Not recorded; see the report | None open | Findings: 2 medium 2 fixed | GitHub ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 1 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 3 |
| Low | 0 | 0 | 0 |
The reports name a repository or files. Open a report to see its scope.
Trustblock holds 2 public audit reports for SP1 Helios, dated 17 Jul 2025 to 29 Jul 2025. The latest is by Zellic (“SP1 Helios”).
Zellic wrote the 2 reports Trustblock holds for SP1 Helios.
1 finding is still open or acknowledged in the firms’ reports: 1 critical. Of 1 critical finding: 1 acknowledged, not fixed. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="sp1-helios"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us