Disclosure SLA public
Spiko's assessment for RD-F-176 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No published acknowledgment-time SLA found. No mention of 72-hour ack window, 90-day disclosure deadline, or coordinated-disclosure timeline in any public Spiko documentation (docs.spiko.io, tech.spiko.io, GitHub, or blog). Follows directly from F175: if no disclosure channel exists, no SLA can be published. Consistent with circle-usyc finding where F176 was also red.
Sources #
- URL
- Spiko Technical Blogtech.spiko.io — no security SLA or disclosure process found in engineering blog postsretrieved 2026-05-16
Methodology #
Determine whether the protocol publishes an acknowledgment-time SLA for disclosed vulnerabilities (e.g., 72h ack).
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol spiko factor RD-F-176 score red collected_at 2026-05-15 22:52:13