Een waakhond blaft niet

[github-actions]

2 guards are not running.

heartbeat.yml - the hourly proof that a file still transfers and a document still signs

• RED: the switch is off: repository variable HEARTBEAT_ENABLED is not "true", so every scheduled run of heartbeat.yml skips the job "heartbeat - production". A skipped job is grey, not red, and notifies nobody. The last 25 scheduled runs have been skipped.
• RED: no scheduled run of "heartbeat - production" has succeeded in the last 25 scheduled runs (most recent conclusion: skipped). the hourly proof that a file still transfers and a document still signs is not being proved by anything.
• to turn it on: gh secret set PARAMANT_CANARY_KEY && gh secret set PARASIGN_CANARY_KEY && gh variable set HEARTBEAT_ENABLED --body true

security-posture.yml - the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route

• RED: the switch is off: repository variable SECURITY_POSTURE_ENABLED is not "true", so every scheduled run of security-posture.yml skips the job "security posture, production". A skipped job is grey, not red, and notifies nobody.
• RED: no scheduled run of "security posture, production" has succeeded in the last 4 scheduled runs (most recent conclusion: skipped). the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route is not being proved by anything.
• to turn it on: gh variable set SECURITY_POSTURE_ENABLED --body true

A guard that cannot fire is worse than no guard, because it produces calm.
This issue stays open, and is updated once a day, until every guard above is running.

Run: https://github.com/Apolloccrypt/paramant-relay/actions/runs/34030779709

2026-09-06T11:37:37.869Z

[github-actions]

2 guards are not running.

heartbeat.yml - the hourly proof that a file still transfers and a document still signs

• RED: the switch is off: repository variable HEARTBEAT_ENABLED is not "true", so every scheduled run of heartbeat.yml skips the job "heartbeat - production". A skipped job is grey, not red, and notifies nobody. The last 30 scheduled runs have been skipped.
• RED: no scheduled run of "heartbeat - production" has succeeded in the last 30 scheduled runs (most recent conclusion: skipped). the hourly proof that a file still transfers and a document still signs is not being proved by anything.
• to turn it on: gh secret set PARAMANT_CANARY_KEY && gh secret set PARASIGN_CANARY_KEY && gh variable set HEARTBEAT_ENABLED --body true

security-posture.yml - the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route

• RED: the switch is off: repository variable SECURITY_POSTURE_ENABLED is not "true", so every scheduled run of security-posture.yml skips the job "security posture, production". A skipped job is grey, not red, and notifies nobody.
• RED: no scheduled run of "security posture, production" has succeeded in the last 5 scheduled runs (most recent conclusion: skipped). the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route is not being proved by anything.
• to turn it on: gh variable set SECURITY_POSTURE_ENABLED --body true

A guard that cannot fire is worse than no guard, because it produces calm.
This issue stays open, and is updated once a day, until every guard above is running.

Run: https://github.com/Apolloccrypt/paramant-relay/actions/runs/34127548963

2026-09-07T13:28:53.852Z

[github-actions]

2 guards are not running.

heartbeat.yml - the hourly proof that a file still transfers and a document still signs

• RED: the switch is off: repository variable HEARTBEAT_ENABLED is not "true", so every scheduled run of heartbeat.yml skips the job "heartbeat - production". A skipped job is grey, not red, and notifies nobody. The last 30 scheduled runs have been skipped.
• RED: no scheduled run of "heartbeat - production" has succeeded in the last 30 scheduled runs (most recent conclusion: skipped). the hourly proof that a file still transfers and a document still signs is not being proved by anything.
• to turn it on: gh secret set PARAMANT_CANARY_KEY && gh secret set PARASIGN_CANARY_KEY && gh variable set HEARTBEAT_ENABLED --body true

security-posture.yml - the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route

• RED: the switch is off: repository variable SECURITY_POSTURE_ENABLED is not "true", so every scheduled run of security-posture.yml skips the job "security posture, production". A skipped job is grey, not red, and notifies nobody.
• RED: no scheduled run of "security posture, production" has succeeded in the last 6 scheduled runs (most recent conclusion: skipped). the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route is not being proved by anything.
• to turn it on: gh variable set SECURITY_POSTURE_ENABLED --body true

A guard that cannot fire is worse than no guard, because it produces calm.
This issue stays open, and is updated once a day, until every guard above is running.

Run: https://github.com/Apolloccrypt/paramant-relay/actions/runs/34224252796

2026-09-08T12:07:05.382Z

[github-actions]

2 guards are not running.

heartbeat.yml - the hourly proof that a file still transfers and a document still signs

• RED: the switch is off: repository variable HEARTBEAT_ENABLED is not "true", so every scheduled run of heartbeat.yml skips the job "heartbeat - production". A skipped job is grey, not red, and notifies nobody. The last 30 scheduled runs have been skipped.
• RED: no scheduled run of "heartbeat - production" has succeeded in the last 30 scheduled runs (most recent conclusion: skipped). the hourly proof that a file still transfers and a document still signs is not being proved by anything.
• to turn it on: gh secret set PARAMANT_CANARY_KEY && gh secret set PARASIGN_CANARY_KEY && gh variable set HEARTBEAT_ENABLED --body true

security-posture.yml - the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route

• RED: the switch is off: repository variable SECURITY_POSTURE_ENABLED is not "true", so every scheduled run of security-posture.yml skips the job "security posture, production". A skipped job is grey, not red, and notifies nobody.
• RED: no scheduled run of "security posture, production" has succeeded in the last 7 scheduled runs (most recent conclusion: skipped). the nightly scan of the public surface: DNS, TLS, headers and the closed ParaID route is not being proved by anything.
• to turn it on: gh variable set SECURITY_POSTURE_ENABLED --body true

A guard that cannot fire is worse than no guard, because it produces calm.
This issue stays open, and is updated once a day, until every guard above is running.

Run: https://github.com/Apolloccrypt/paramant-relay/actions/runs/34350234210

2026-09-09T12:18:28.617Z