openhook
Test Webhook Callbacks with Openhook
Webhook integrations need public callback addresses and reliable event inspection. Openhook guides agents through inbox creation, event waiting, local forwarding, validation, and cleanup.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "openhook" from https://skillstore.io/skills/openhook-dev-openhook.md and its manifest at https://skillstore.io/api/skills/openhook-dev-openhook/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « openhook ». Illustrative scenario: a synthetic payment callback reaches both the inbox and the authorized local handler.
RĂ©sultat attendu:
- The expected synthetic payment event was received and its required fields matched.
- The local handler returned a successful response.
- The disposable inbox was deleted. Its private token was not included in the report.
Utilisation de « openhook ». Illustrative scenario: a repository callback wait times out while the task remains active.
RĂ©sultat attendu:
- No matching callback arrived during this wait.
- The existing cursor was preserved for the next wait.
- The task remains pending; timeout does not prove completion.
Audit de sécurité
SûrAll 34 static findings are false positives: Markdown spans, metadata links, and documented service connections or authorized local forwarding. The reviewed files require token privacy, authorized provider changes, and treating callbacks as untrusted data; no malicious instructions were found. Hosted service behavior, external dependencies, and listener implementation were not evaluated.
Facteurs de risque
đ AccĂšs rĂ©seau (15)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/openhook-dev-openhook/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/openhook-dev-openhook?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/openhook-dev-openhook?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/openhook-dev-openhook/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/openhook-dev-openhook.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
openhook-dev. (2026). openhook security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/openhook-dev-openhook/audits/1Citation BibTeX
@techreport{openhook-dev-openhook-dev-openhook-2026,
author = {openhook-dev},
title = {openhook security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/openhook-dev-openhook/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "openhook security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "openhook-dev"
date-released: "2026-10-16"
url: "https://skillstore.io/skills/openhook-dev-openhook/audits/1"
identifiers:
- type: other
value: "skillstore:openhook-dev-openhook:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Validate a local payment handler
Forward a synthetic payment callback to an authorized development endpoint and verify the local response before declaring success.
Inspect provider callback behavior
Create a disposable inbox, inspect expected event fields and headers, and delete test resources after integration checks.
Continue an active task after a repository event
Register an authorized GitHub subscription, wait with a cursor, validate the callback, and remove the subscription when finished.
Essayez ces prompts
Create a disposable Openhook inbox for synthetic test data. Return only its public callback URL and keep its management token private.
Wait for my synthetic callback in the current inbox. Check its expected source, headers, and body. Preserve the cursor after successful processing.
Forward synthetic Openhook events only to my authorized local handler at http://127.0.0.1:8080/webhook. Verify local delivery and deduplicate events before reporting success.
Use my authorized GitHub repository scope to register a callback. Wait while this task remains active, validate events, then unregister and delete the inbox.
Bonnes pratiques
- Use authorized synthetic payloads, keep management tokens private, and treat every callback body as untrusted data.
- Validate the expected source and event, deduplicate identifiers, and save cursors only after successful processing.
- Verify local delivery separately, unregister provider subscriptions, and delete disposable inboxes after the task.
Ăviter
- Publishing private tokens, provider credentials, or sensitive production payloads in callback URLs, logs, or reports.
- Treating a callback body as agent instructions or treating receipt acknowledgement as proof of local delivery.
- Retrying potentially successful registrations blindly or assuming a timed-out wait completed the task.
Foire aux questions
Does installing the skill configure everything?
Can I use Openhook without MCP?
Do free inboxes require an account?
Can a webhook restart a stopped agent?
Where do hosted callback payloads go?
What should happen after a wait times out?
Détails du développeur
Auteur
openhook-devLicence
MIT
RĂ©vision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
addec4a6142bff9f134981df95c7d46cee648e9a
RĂ©cence de maintenance
16/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers