Last updated October 24, 2026

Trust

Current, bounded evidence for one named Cadence source commit and its production deployments.

Current verification results

These checks are bounded, time-specific evidence. They do not certify Cadence or prove that defects are absent.

Deployment summary

Source commit
967812093da1b6f725f3dd553e9eac93f3af4dec
Application deployment
dpl_6TqYhYrVDbR7wXmGitUVyN1g4wAm
Marketing deployment
dpl_AXpnqMUkHcGkmbUWwex1gznqH5RD
Build time
Nov 18, 2026, 4:25 PM UTC
Verification time
Nov 18, 2026, 4:25 PM UTC
Snapshot fresh until
Nov 19, 2026, 4:25 PM UTC

Build and supply chain

Source to deployment provenance

Status: Stale

Both Ready deployments name the expected source commit.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
Both named Ready Vercel deployments and their public Git commit metadata.
Limit:
It does not prove that later configuration or provider state is unchanged.
Open immutable evidence for Source to deployment provenance

Production dependency scanning

Status: Failed

SBOM has 268 components with SHA-256 7f4d1cb6c25ef3908c429a5880ad6f0076c6e7d46e37ce679a2d7c0338ed4952; audit totals: 10 (0 critical, 9 high, 1 moderate, 0 low); Dependabot open aggregate 5.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
Production dependencies declared by the lockfile, npm advisory data, and Dependabot status.
Limit:
It covers declared production dependencies and the tool's data at completion time only.
Open immutable evidence for Production dependency scanning

Code scanning

Status: Stale

CodeQL completed for the named commit and reported zero open repository alerts.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
Configured GitHub code-scanning analyzers for the named public repository and source commit.
Limit:
It covers configured analyzers and rules only and cannot establish the absence of defects.
Open immutable evidence for Code scanning

Secret scanning

Status: Unavailable

The provider did not expose a safe aggregate result.

Reason: The collector could not read a complete aggregate provider result.

Timestamp:
Not available
Scope:
GitHub secret scanning and push protection for the named public repository.
Limit:
It covers patterns and repository history visible to the configured platform only.
Open immutable evidence for Secret scanning

Public route integrity

Public artifact integrity

Status: Stale

6 of 6 public assets matched status, type, size, and digest bounds.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
6 allowlisted public application and marketing assets.
Limit:
It covers generated public files, not private operational records or live-route availability.
Open immutable evidence for Public artifact integrity

Application routes

Status: Stale

10 of 10 application routes matched the registry.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
10 explicit unauthenticated application route contracts.
Limit:
It covers the sampled routes and responses at completion time, not every authenticated workflow.
Open immutable evidence for Application routes

Marketing routes

Status: Stale

79 of 79 marketing routes matched the generated manifest.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
79 generated marketing HTML and Markdown route contracts.
Limit:
It covers declared marketing routes at completion time, not every external cache or network path.
Open immutable evidence for Marketing routes

Hosted data boundaries

Hosted migration boundary

Status: Stale

Hosted migration boundary matches 20261117105000.

Timestamp:
Nov 18, 2026, 4:25 PM UTC
Scope:
Hosted Supabase migration history compared with the tracked migration boundary.
Limit:
It proves migration-history alignment only, not correctness of user-owned data.
Open immutable evidence for Hosted migration boundary

Cross-account RLS isolation

Status: Not run

The authorized cross-account RLS smoke did not run in this collection.

Timestamp:
Not available
Scope:
Disposable-account ordinary-client ownership checks across the public data API.
Limit:
It covers only the tested tables and operations at completion time.
Open immutable evidence for Cross-account RLS isolation

Service dependencies

ServicePurposeBoundary
VercelApplication and marketing hostingReceives deployment and request data.
SupabasePostgres storage and authenticationStores account and behavior records behind Row Level Security.
Google AuthGoogle account sign-inProvides the identity used by Supabase Auth.
Browser pushBrowser remindersOptional; depends on browser permission and a push subscription.
SequenzyEmail remindersOptional; used only when email reminders are enabled.

Data boundaries

Cadence stores account and behavior records in Supabase. Row Level Security scopes user-owned records to the authenticated account.

Exports go only where the user downloads or shares them; Cadence does not send an export to an AI provider. Optional Daily Brief sends the context described in the Privacy Policy to OpenAI, including Calendar timing only after a separate choice. A connected AI client receives tracking records through MCP only after the user authorizes it. Cadence does not use Google user data to train AI models. Local connector tests do not verify live providers, installed desktop behavior or deployment.

Public source and license

Cadence source code is public at github.com/emixd12/cadence under the repository's MIT license.

The public source lets anyone inspect the implementation. It does not independently verify a hosted deployment.

Limits of verification

Each result covers only its named scope, source commit, deployments, and verification time. A Passed result is not a certification or a guarantee that defects are absent.

Provider configuration, later changes, untested workflows, and private operational records remain outside a result unless its scope states otherwise.