Repository navigation
Conversation
#400) * content(opsec): endpoint security tiers and DPRK liveness verification - Add endpoint security device provisioning tiers (managed, VDI, enterprise browser) - Add deepfake liveness verification techniques to DPRK TTP page - Add andrew-chang-gu to contributors.json (username TBD) Co-authored-by: DicksonWu654 <dickson@certik.com> Co-authored-by: andrew-chang-gu <> * chore: fill andrew-chang-gu contributor fields from public LinkedIn profile * Add contributor Andrew Chang-Gu to contributors.json Added new contributor Andrew Chang-Gu with details. --------- Co-authored-by: DicksonWu654 <dickson@certik.com> Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* Add password manager endpoint hardening guide * Tone down password manager hardening guide * Shorten password manager hardening guide * Make wallet secret storage guidance explicit * Remove decorative separators from password manager hardening guide * Fix lint in password manager endpoint guide * Tighten password manager endpoint guide * Shorten password manager endpoint guide * Clarify password manager endpoint guidance * Add password manager endpoint hardening guide * Tone down password manager hardening guide * Shorten password manager hardening guide * Make wallet secret storage guidance explicit * Remove decorative separators from password manager hardening guide * Fix lint in password manager endpoint guide * Tighten password manager endpoint guide * Shorten password manager endpoint guide * Clarify password manager endpoint guidance * Expand password manager hardening scope * Revert "Expand password manager hardening scope" This reverts commit 4bf04d6. * docs: tighten password manager browser guidance --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* Add hardware security key guide * Credit Opsek authors on YubiKey guide * Remove decorative separators from hardware security keys guide * Fix lint in hardware security keys guide * Tighten hardware security keys guide * Move hardware security keys guide to endpoint security * Tighten hardware keys guide metadata * Update hardware-security-keys.mdx * Update hardware-security-keys.mdx * Add hardware security key guide * Credit Opsek authors on YubiKey guide * Remove decorative separators from hardware security keys guide * Fix lint in hardware security keys guide * Tighten hardware security keys guide * Move hardware security keys guide to endpoint security * Tighten hardware keys guide metadata * Add YubiKey-specific setup guidance * docs: tighten hardware key setup guidance * Delete AGENTS.md --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* Add stewards for Incident Management and AI Security fws * sync contributors company
* Add SSH client and key management hardening guide * Remove decorative separators from SSH hardening guide * Fix markdownlint spacing in SSH hardening guide * Tighten SSH hardening guide * Shorten SSH hardening guide * Clarify SSH hardening guidance * Introduce SSH certificates for better key management Added a section on using SSH certificates for improved access management. * Clarify SSH host verification guidance * Fix SSH guide markdown formatting * Finish SSH guide review fixes * Add SSH client and key management hardening guide * Remove decorative separators from SSH hardening guide * Fix markdownlint spacing in SSH hardening guide * Tighten SSH hardening guide * Shorten SSH hardening guide * Clarify SSH hardening guidance * Introduce SSH certificates for better key management Added a section on using SSH certificates for improved access management. * Clarify SSH host verification guidance * Fix SSH guide markdown formatting * Finish SSH guide review fixes * Trim unrelated SSH wordlist entries * Update wordlist.txt * Add reviewers to SSH client hardening guide --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* add github workflow to autmatically upload images to S3 * implement review + deps revamp * Reorganize AWS credentials configuration in workflow * Add --ignore-scripts to install step for supply chain attack mitigation --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* Added MFA overview, and updated contributors file. * Build fix and language updates. * Refine MFA overview and recommendations Revised language for clarity and emphasis on MFA importance. Updated recommendations for MFA methods and highlighted security considerations for passkeys. * Further clarification about passkey storage. --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
Co-authored-by: frameworks-volunteer <jamesbond777bot@duck.com>
* Port cert revisions and add SFC Identity & Accounts
Mirrors the revisions applied in the SEAL-Certs-Template repo (see its
CHANGELOG.md for full detail). Summary:
- sfc-multisig-ops: ms-2.1.2 strengthened from "evaluate" to "implement";
ms-4.1.1 transaction process consolidated 8 to 5 bullets
- sfc-treasury-ops: scope note added; per-actor/per-path exposure limits
(tro-2.1.3) and privileged access / root account management (tro-3.1.5)
added; trusted-parser bullet on tro-4.1.1; various consolidations and
softening (session timeouts, impact thresholds, exposure limits)
- sfc-devops-infrastructure: di-1.1.4 split into process + di-1.1.5 list;
runner hardening on di-3.1.1; network architecture on di-4.1.1; supply
chain mention softened; References section added
- sfc-dns-registrar: dns-3.1.1 slimmed to reference the new Identity &
Accounts cert for account management
- sfc-incident-response: four IR controls consolidated (team roles,
contacts, alerting, drills); header reference to Identity & Accounts
- sfc-identity-accounts (NEW): horizontal cert covering organizational
account management (inventory, phishing-resistant MFA, credential
management, recovery methods, lifecycle, takeover monitoring, third-
party access)
Control IDs are stable; no renames. Baseline text changes do not affect
workbook import (keyed on control ID).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Retire SFC Workspace Security; wire in Identity & Accounts
The old Workspace Security cert drifted far from SEAL's SME (device
management, EDR/MDM, physical/travel security, formal training programs).
Its crypto-relevant content (account inventory, phishing-resistant MFA,
credential management, account lifecycle, takeover monitoring) is now in
the new horizontal Identity & Accounts cert. Generic enterprise IT
coverage is better left to ISO 27001 / SOC 2 / CIS.
- Delete docs/pages/certs/sfc-workspace-security.mdx
- vocs.config.tsx: sidebar updated (add Identity & Accounts, remove
Workspace Security)
- utils/generate-cert-data.js: CERT_ORDER updated so the overview-page
"Export All Certifications" xlsx includes I&A and excludes Workspace
- utils/generate-printable-checklists.js: CERT_META updated so the Print
button generates an I&A checklist and no longer generates one for
Workspace
- components/certified-protocols/CertifiedProtocols.tsx: certTypeToName
map updated (sfc-ida replaces sfc-ws)
- docs/pages/certs/overview.mdx: cert list updated
- docs/pages/certs/index.mdx: cert list updated
- docs/pages/intro/overview-of-each-framework.mdx: cert list updated
The fetched-tags.json and cert-data.json artifacts regenerate at build
time.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Surface control IDs in the control card UI
Control IDs (e.g., ms-2.1.2) are already in the data model and used by
workbook import/export and aria attributes, but were invisible in the
rendered card. Surface them inline next to the title so readers and
reviewers have a stable reference they can cite.
- ControlCard.tsx: render {control.id} before the title with a muted
separator
- control.css: .control-id styled muted, monospace, 0.875em; .control-id-sep
muted, non-bold
No behavioral change; purely additive display.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Add per-cert version stamps and central changelog
Protocols that have certified against an earlier version of a cert need
to scope the delta when that cert is revised. Adds explicit versioning
so re-certification decisions are data-driven.
- Per-cert frontmatter fields: version (semver-ish) and revised (ISO
date). Rendered inline near the H1 title: "Revision X.Y · Updated
YYYY-MM-DD · Changelog".
- New page: docs/pages/certs/changelog.mdx aggregating revision history
across all certs with inaugural 2026-04-17 entry covering the
feedback-integration-1.1 changes.
- vocs.config.tsx: Changelog added to sidebar under SEAL Certifications.
All five existing certs stamped at v1.1 (revised 2026-04-17). New
Identity & Accounts cert stamped at v1.0.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Regenerate build artifacts
- docs/pages/certs/index.mdx: generate-folder-indexes added Changelog row
- utils/fetched-tags.json: tags-fetcher regenerated tag map (added
/certs/changelog entry; workspace-security replaced by
identity-accounts; sectionMappings sort order shuffled)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Add ir-2.1.1 threat model to Incident Response
Monitoring coverage is only meaningful if it's pointed at the right
things. The existing IR cert had team structure, contacts, monitoring,
alerting, and playbooks, but no control requiring an explicit threat
picture of protocol operations and external dependencies. This control
closes that gap and anchors the monitoring and playbook controls to a
known threat model.
- Insert new ir-2.1.1 (Threat Model for Protocol Operations) at the
start of Section 2 (Monitoring, Detection & Alerting)
- Existing Section 2 controls shifted: old ir-2.1.1 to ir-2.1.2,
ir-2.1.2 to ir-2.1.3, ir-2.1.3 to ir-2.1.4
- Evidence Tracker count 13 to 14 (template repo only)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Rewrite certs overview to align with program roadmap
The previous overview was written during RFC Phase (ended Dec 31, 2025)
and framed certifications as "proposed" and "being developed." The
framework is now stable, published, and moving into active certification
with accredited firms.
Rewritten to:
- Open with the same framing as the internal program-and-roadmap doc:
code audits don't catch operational failures, certifications target
that gap
- List the six modules (with the new Identity & Accounts and Incident
Response updated to include threat modeling)
- Condense "How Certification Works" into a five-step engagement flow
with EAS attestation
- Replace the RFC Phase section with a plain Program Status summary of
where the program is now
- Trim outdated FAQ items (the "Q1 2026 rollout" question) and update
wording throughout
- Link to the new /certs/changelog page for revision history
Shorter overall; aligned with the roadmap doc without duplicating its
operational detail.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Add back protocol and auditor signup links to certs overview
Previous rewrite dropped these along with the RFC Phase framing. Adding
them back as a tight "Get Involved" section between Program Status and
FAQ.
Both entry points currently point at the same typeform
(securityalliance.typeform.com/CertsAuditor), matching the original
overview page. If protocols and auditors need distinct intake forms
later, the URL can be updated.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Integrate PR feedback from template repo review
Mirrors template-repo commits acddf5c, 2d3a777, 5ae8d0f which applied
DicksonWu654's review feedback. Since v1.1 hasn't shipped yet, the
changelog entry for v1.1 is updated to reflect final state rather than
documenting an intra-PR iteration.
- sfc-devops-infrastructure: di-1.1.2 drops the supply-chain
parenthetical (Section 2 already handles supply chain); di-1.1.4 and
di-1.1.5 merged back into a single di-1.1.4 covering both the tool
approval process and the approved-tools list; References section at
the bottom removed (other certs don't carry References, so the
inconsistency wasn't earning its keep)
- sfc-identity-accounts: ida-2.1.1 drops the "(subject to SIM-swap and
interception)" parenthetical; ida-4.1.1 drops the inline "(coordinated
with SFC - Incident Response monitoring)" parenthetical (the trailing
IR coordination bullet still carries that point); "Related certs"
list in the page body removed (cross-refs live inline in each
vertical cert)
- sfc-incident-response: ir-2.1.1 threat model gains a baseline bullet
on identifying single points of failure and highly centralized
components across onchain and offchain layers (cross-chain messaging
providers, oracle providers, critical infrastructure dependencies)
- changelog.mdx: v1.1 entry updated to reflect final merged state;
DevOps control count is now unchanged at 16, workbook compat note
flags the shifted IR Section 2 IDs
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Fix protocol signup typeform URL to CertsWaitlist
Both the protocol and auditor signup links in the certs overview were
pointing at the same auditor form (CertsAuditor). Protocols should
land on the waitlist form (CertsWaitlist) instead. Per PR #459 review
comment from DicksonWu654.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ns alphabetical order in fetched tags (#441)
* Add Attack Surface Overview page with interactive radial threat map Visual security posture dashboard showing 12 attack vectors as a radial diagram. Nodes are color-coded (red/amber/green) by posture state with click-to-toggle and localStorage persistence. Clicking a node opens a detail card with description, attack tags, and framework guide links. Designed for CSOs to quickly assess and communicate security gaps. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Mark Attack Surface Overview as dev content Adds dev: true flag to sidebar entry per contributing guidelines. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Replace selection ring with scale + glow effect on selected nodes Selected nodes now scale up 10% and show a soft color-matched glow instead of a detached ring outline. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Add GitHub Actions reminder for attack surface threat data changes Posts an automated PR comment when threatData.ts is modified, reminding contributors to include all required fields and verify framework links. Follows the same pattern as the existing vocs-config-reminder workflow. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Address Sara first PR feedback item Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Address Sara second PR feedback item Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Smooth-scroll detail card into view when a threat node is clicked Clicking a node on the radial map showed the detail card below the map, but on typical viewports the card landed below the fold, so it wasn't obvious anything had happened. Use scrollIntoView with block: "nearest" on the card when it mounts or the selected vector changes, respecting prefers-reduced-motion. Third PR feedback item addressed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Move attack-surface.mdx into intro/ folder and update links Moved the page to sit alongside the other Introduction pages. Updated sidebar link, internal cross-link in how-to-navigate, and component import path to match the new location. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Use react-router Link for framework CTA to avoid full page reload The detail card's framework link used a plain <a> tag which caused a full page reload. Switched to react-router-dom's <Link> for client-side navigation, consistent with the rest of the site. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Add standard page components to Attack Surface Overview Adds TagProvider, TagFilter, TagList, and ContributeFooter to match the pattern used by all other Introduction pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…annel scope (#445) Clarify that profile labels and platform status indicators are not proof of legitimacy, and state that unsupported platforms should be explicitly identified.
Adds TxScope to monitoring tools and wallet security tools pages. TxScope is a Solana-native pre-signing transaction threat scanner for Squads Protocol multisigs, filling the non-EVM tooling gap noted in the current tools page. Co-authored-by: black <bob@bobby.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Clarify hot vs cold wallet taxonomy * Narrow hot vs cold wallet edits --------- Co-authored-by: welttowelt <welttowelt@users.noreply.github.com>
* Add third party script security page in the frontend web app fw * fix Further Reading link * Fix links in web3-supply-chain-threats.mdx
* weekly cleanup: - sync badges - fix outputs spellchecker - fix outputs linter - sync contributing files - sync tags * Cleanup of the latest PR merged * sync contributor badges with latest PRs * Fix indentation
…dates (#425) Bumps the npm_and_yarn group with 2 updates in the / directory: [dompurify](https://github.com/cure53/DOMPurify) and [flatted](https://github.com/WebReflection/flatted). Updates `dompurify` from 3.3.0 to 3.3.3 - [Release notes](https://github.com/cure53/DOMPurify/releases) - [Commits](cure53/DOMPurify@3.3.0...3.3.3) Updates `flatted` from 3.3.3 to 3.4.2 - [Commits](WebReflection/flatted@v3.3.3...v3.4.2) --- updated-dependencies: - dependency-name: dompurify dependency-version: 3.3.3 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: flatted dependency-version: 3.4.2 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
- code-signing.mdx: Add GPG key generation, subkeys, YubiKey setup, passphrase management, key backup/recovery - continuous-integration-continuous-deployment.mdx: Add SLSA provenance, SBOM generation, OIDC federation for cloud access - repository-hardening.mdx: Add CODEOWNERS patterns, GitHub Advanced Security (CodeQL, secret scanning, dependency review), security policy template - security-testing.mdx: Add severity thresholds table, Semgrep custom rules, false positive management, coverage and mutation testing
- Update contributors frontmatter: mattaereal as author, scode2277 as reviewer - Replace discontinued keys.mailvelope.com with keyserver.ubuntu.com - Fix CISA link text to match URL (Software Bill of Materials) - Update expired nosemgrep example date to 2027-06-01 - Add note about simplified Semgrep rule example
The search index lives in docs/dist/.vocs/ (a hidden directory). actions/upload-artifact@v4 excludes hidden files by default, so the .vocs directory was missing from the uploaded artifact. This caused the search index to be absent from preview deployments, breaking the native search (/) on all preview URLs. Adding include-hidden-files: true ensures the .vocs directory (and any other hidden assets) are included in the artifact.
* feat: add llms.txt generator + llms-{framework}.txt for all the frameworks we have + changed titles to 2 pages as previously confusing
* Add branch-aware links + better hadle of contributing folder
* fix: making the generator inherit dev:true from parent sidebar blocks
* refactor: restructure llms output with per-page files, folder layout, and tighter routing index
* fix: make branch check stronger
…els (#473) * fix: expand VPN services page with HTTPS vs VPN, metadata, threat models (closes #406) * Update docs/pages/privacy/vpn-services.mdx Co-authored-by: Sara Russo <sararusso984@gmail.com> * refactor: split VPN services into subcategory pages per review feedback Restructure vpn-services.mdx into a vpns/ directory with sub-pages: - overview.mdx: entrance page with intro and links to subsections - https-vs-vpn.mdx: HTTPS vs VPN comparison and metadata gap - attack-surfaces-public-networks.mdx: public Wi-Fi risks - when-to-use-vpn.mdx: threat model decision framework + choosing a VPN - vpn-limitations.mdx: VPN limitations and DNS leaks - vpn-providers-and-tools.mdx: recommended providers, tools, and resources Update vocs.config.tsx with nested sidebar structure for VPN Services. All new pages include outline: deep for subsection navigation. --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com> Co-authored-by: Sara Russo <sararusso984@gmail.com>
…dates (#464) Bumps the npm_and_yarn group with 3 updates in the / directory: [axios](https://github.com/axios/axios), [dompurify](https://github.com/cure53/DOMPurify) and [hono](https://github.com/honojs/hono). Updates `axios` from 1.14.0 to 1.15.0 - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.14.0...v1.15.0) Updates `dompurify` from 3.3.3 to 3.4.1 - [Release notes](https://github.com/cure53/DOMPurify/releases) - [Commits](cure53/DOMPurify@3.3.3...3.4.1) Updates `follow-redirects` from 1.15.11 to 1.16.0 - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.11...v1.16.0) Updates `hono` from 4.12.12 to 4.12.14 - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.12.12...v4.12.14) --- updated-dependencies: - dependency-name: axios dependency-version: 1.15.0 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: dompurify dependency-version: 3.4.1 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: follow-redirects dependency-version: 1.16.0 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: hono dependency-version: 4.12.14 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
sync badges sync indexes sync tags fix spellchecker outputs fix linter outputs Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
Extract §4 (Upgrade Governance) out of data-security-upgrade-checklist
into a standalone DevSecOps page focused on smart-contract upgrade
governance across the full proposal lifecycle. Add an interactive hero
graphic mapping threats onto a 4-stage SDLC, replace raw-markdown
checklists with a stateful ChecklistItem component, and extend the
content with material that consistently fails in practice but rarely
appears on upgrade checklists: invariant suites that run against live
mainnet state, and reproducible onchain calldata verified by CI.
Page: /devsecops/governance-proposal-security
Stages: Plan -> Build and Test -> Review & Audit ->
Propose, Verify Onchain Calldata & Monitor
New components:
- <GovernanceSDLCPipeline /> - SVG pipeline with threat constellations,
click-to-expand detail panel, keyboard nav, loop-back "feeds next
cycle" arrow. Reuses categoryMeta from attack-surface for visual
consistency. Stateless.
- <ChecklistItem title="..."> ... </ChecklistItem> - interactive
labelled checkbox with localStorage-persisted state and
aria-describedby. Replaces every raw markdown "- [ ]" item on the
new page.
Migrations:
- docs/pages/devsecops/data-security-upgrade-checklist.mdx - section 4
removed; page renamed to "Data Security Checklist" (URL preserved).
- docs/pages/devsecops/overview.mdx - dropped duplicate "What's inside
DevSecOps" section; Contents list is the single entry point (8
entries including the new page and Isolation & Sandboxing).
- vocs.config.tsx - sidebar entry added and old Data Security entry
renamed.
- components/index.ts - exports the two new components.
Notable content:
- Stage 2: tests must exercise the actual deployment script, and
fork-tests must execute the proposal's calldata at HEAD before
running the integration + invariant suite.
- Stage 3: internal peer review of the proposal by a non-author
reviewer; audit scope extends to deploy scripts and proposal payloads.
- Stage 4: reproducible calldata built locally + rebuilt in CI,
compared byte-for-byte against what's onchain.
- Real-World Proposal Failures: Wormhole (Feb 2022), Nomad (Aug 2022),
Compound cETH Proposal 117 (Aug 2022), Yearn Finance yUSDT (Apr 2023)
- each framed around a specific SDLC failure mode.
Contributors:
- wrote: quillaudits, dickson, ElliotFriedman
- fact-checked: mattaereal
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* docs(devsecops): normalize structure and wording Align DevSecOps pages with the content model: fact-checked role, canonical Key Takeaways, overview sidebar map, Further reading headings, and chrome fixes (footer on developer confinement, IDE/data checklist takeaways). * docs: drop invented contributor credits Match develop authorship exactly. Clear wrote/reviewed/fact-checked arrays where normalization invented authors on pages that had none. Do not attribute chrome-only edits as content authorship. * docs: add Further Reading sections for validate:content Child pages missing a canonical further/related H2 failed the updated #561 validator. Add a minimal Further Reading block linking the framework overview. * docs: clear remaining validate:content failures for #561 Neutralize fence comments that look like headings, canonicalize overview page-map titles, clamp descriptions, demote excess H2s, and mark template pages with content-model exceptions. * expand further reading sections + fix headings + fix comments in code blocks * add all required frontmatter + removed unnecessary blank lines + fixed imports and components usage --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
* docs(opsec): normalize structure and wording Align active OpSec pages to the SEAL content model: frontmatter bands, canonical Key Takeaway, chrome components, stub scaffolds, and overview maps. Exclude old/ and generated indexes. Editorial only. * docs(opsec): drop invented authorship; restore fact-check credit Keep contributor usernames exactly as on develop. Clear wrote where normalization had invented mattaereal on pages with no prior credits. Restore fact-checked: [mattaereal] on secure-operating-systems. * docs: align further-reading headings with validate:content Rename Further Reading H2s to the exact title the updated #561 validator accepts; sentence-case a few common section headings. * docs: add Further Reading sections for validate:content Child pages missing a canonical further/related H2 failed the updated #561 validator. Add a minimal Further Reading block linking the framework overview. * docs: clear remaining validate:content failures for #561 Neutralize fence comments that look like headings, canonicalize overview page-map titles, clamp descriptions, demote excess H2s, and mark template pages with content-model exceptions. * docs(opsec): exception nested overviews missing page maps * Expand further reading sections + fix headings in code blocks + fix imports and components * fix frontmatter titles and descriptions for opsec/old * Fix cutted description + headings structure --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
* Standardization sweep on supply-chain framework * standardize overview page + add citations + populate wordlist for cspell
* docs(physical-security): normalize structure and wording Canonical Key Takeaways, description band, Related frameworks on overviews, checklist takeaway, line-length and chrome cleanup across the framework and coercion & duress subtree. Stub overviews preserved. * docs: add Further Reading sections for validate:content Child pages missing a canonical further/related H2 failed the updated #561 validator. Add a minimal Further Reading block linking the framework overview. * docs: clear remaining validate:content failures for #561 Neutralize fence comments that look like headings, canonicalize overview page-map titles, clamp descriptions, demote excess H2s, and mark template pages with content-model exceptions. * docs(physical-security): exception stub nested overviews missing page maps * Expand further reading sections + add indexes and tags as missing * fix CI by transforming html comments in JSX --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
* fix: add placeholder message for pages with no contributors (closes #593) When a page has contributor roles defined but all user lists are empty, the AttributionList component rendered an empty styled container with no content. Now displays a "No contributors yet" placeholder with a link to the contributing guide, improving UI/UX for new or unstewarded pages. * Make the contribution call appear even if the contribution block in the frontmatter is present + substitute <a> tag with <Link> to do not trigger a reload --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
…posure) (#616) * docs(devsecops): add developer-targeted intrusion guidance * docs(devsecops): fix attribution and strengthen procedure modality Attribute DTI authorship to blackbigswan with mattaereal as reviewer. Retain prior IDE authors and add blackbigswan. Add must/should/may wording to the untrusted-code handling procedure. * docs(devsecops): align DTI title suffix and drop overview author Use | SEAL on handling-untrusted-code to match sibling DTI pages. Keep DevSecOps overview writers empty for the map-only edit. * docs(devsecops): remove blackbigswan from DevSecOps overview attribution * chore: retrigger Cloudflare preview deploy * Remove question related sentence as there are no questions * docs(devsecops): address review feedback on DTI pages Add core principles section to overview (ElliotFriedman's suggestion: distill time pressure, multi-channel verification, and isolation into a quick-reference list to reduce cognitive overhead under stress). Add under-pressure callout to handling-untrusted-code linking to the core principles (ElliotFriedman's suggestion on digestibility). Expand compromise response checklist to cover private key and seed phrase exposure — migrate assets to a new wallet from a clean device (AllyPry's suggestion). * docs(devsecops): clarify DTI feedback on isolation and key exposure Tighten isolation principle to call out restricted egress and closed ports (ElliotFriedman's razor). Split private-key/seed-phrase migration into its own compromise-response checklist item so operators cannot miss it under a dense rotation bullet (AllyPry). Mirror isolation specifics in the under-pressure callout. * docs(devsecops): attribute #610 reviewers in DTI frontmatter Add YAML contributors.reviewed entries for the reviewers whose #610 feedback landed in this PR: - overview: ElliotFriedman (core principles), scode2277 - handling-untrusted-code: ElliotFriedman, AllyPry, scode2277 - execution-paths: scode2277 (approved #610) Keep mattaereal; leave wrote as blackbigswan. --------- Co-authored-by: matta <matt@theredguild.org> Co-authored-by: Sara Russo <sararusso984@gmail.com>
* fix(security): weekly dependabot security updates * override cap js-yaml and @babel/core to compatible versions * Sync lock-file with previous overrides --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
* chore: - make further reading sections case sensitive - fix user-team-security position in sidebar - check and fix spellchecker and md linter - fix link in sidebar reminder workflow - remove multiple blank lines - standardize list format with dashes - sync indexes and tags - sync badges * standardize workflows versions to 6.x so dependabot picks the right bumps
#602) Bumps the npm_and_yarn group with 1 update in the / directory: [mermaid](https://github.com/mermaid-js/mermaid). Updates `mermaid` from 11.16.0 to 11.16.1 - [Release notes](https://github.com/mermaid-js/mermaid/releases) - [Commits](https://github.com/mermaid-js/mermaid/compare/mermaid@11.16.0...mermaid@11.16.1) --- updated-dependencies: - dependency-name: mermaid dependency-version: 11.16.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the actions-patch group with 1 update in the / directory: [pnpm/action-setup](https://github.com/pnpm/action-setup). Updates `pnpm/action-setup` from 6.0.9 to 6.0.10 - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@0ebf471...0977fd9) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: 6.0.10 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…dates (#605) Bumps the actions-minor group with 2 updates in the / directory: [actions/checkout](https://github.com/actions/checkout) and [actions/setup-node](https://github.com/actions/setup-node). Updates `actions/checkout` from 5.0.1 to 5.1.0 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5.0.1...fbc6f39) Updates `actions/setup-node` from 6.4.0 to 6.5.0 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@48b55a0...2499707) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 5.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions-minor - dependency-name: actions/setup-node dependency-version: 6.5.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* Add Policy as Code section under DevSecOps Adds docs/pages/devsecops/policy-as-code/ with four pages covering how a policy engine is applied across the CI/CD pipeline, and what NIST SP 800-204D requires of it: - overview: what a policy engine decides, the two evaluation modes (pipeline artifacts versus platform configuration), and the four places the standard names a policy enforcement engine - ci-pipeline: commit, merge, and build gates - release-and-runtime: publishing identity, deployment gates, drift detection - governance: which violations block, who may override, where thresholds come from, and how rules are owned and retired Existing DevSecOps pages document which controls to enable. These cover the decision layer above them, and link out to those pages rather than restating their content. Rego examples are validated against OPA 1.4.2, including the expiring-exception behaviour the governance page relies on. They are fenced as `python` because the site's Shiki bundle has no Rego grammar and an unrecognized language fails the build; the overview page carries a note to that effect. Also: - Registers the section in vocs.config.ts as a nested group with dev: true - Updates the DevSecOps overview contents list - Adds an s1ns3nz0 entry to contributors.json - Adds Rekor to wordlist.txt for the spell check Verified: pnpm run docs:build, cspell, and markdownlint-cli2 all pass. Claude-Session: https://claude.ai/code/session_01CPQ1FcHGiBKWPd8waT7uGx * docs(devsecops): align Policy as Code with the content normalization standard Applies the standard introduced in #561 and the sentence-case heading rule from #595: - Renames 'Further Reading & Tools' to 'Further reading' on all four pages - Renames the overview's page map section to 'What this framework covers' - Moves three Rego comments into the surrounding prose The last change is a workaround rather than an improvement. utils/validate-content.cjs extracts headings without stripping fenced code, so a line-start '#' comment inside a Rego block parses as an H1 and any following H3 is reported as heading_level_skip. Noted on the PR. Claude-Session: https://claude.ai/code/session_01CPQ1FcHGiBKWPd8waT7uGx * docs(devsecops): fix bullet count in Policy as Code overview Address review nit: "Two things have to come from your organization" was followed by three bullets. Merge the trailing bullet into the rule-content item so the count matches. Claude-Session: https://claude.ai/code/session_01CPQ1FcHGiBKWPd8waT7uGx * docs(devsecops): apply review feedback on Policy as Code Address @scode2277's review on #592: - Attribute SP 800-204D precisely: it names a policy enforcement engine as one technique and OPA as an example, rather than "officially recommending" either. - Move the python-fence note off the overview, which has no code blocks, and place it once above the first Rego block on each page that does. - Rewrite the tj-actions passage with the reported figures (23,000+ repos, ~218 leaked secrets, mostly short-lived workflow tokens). - Replace the publish-stage paragraph that restated the "two stages hold by convention" section later on the same page. - Apply RFC modality to all four checklists, per the normative modality rules in docs/pages/contribute/style-and-terminology.mdx. - Trim "The basics" on the overview: fold policy-data detail into its definition, collapse the SSDF and 800-204D descriptions, and drop the bulleted restatement of the enforcement-point consequences. Claude-Session: https://claude.ai/code/session_01CPQ1FcHGiBKWPd8waT7uGx * docs(devsecops): remove second person and Rego fence notes Second round of review feedback on #592: - Drop the three python-fence notes. The fence is a Shiki/vocs grammar gap being tracked upstream by the maintainers, not something readers need explained on the page. - Replace all 24 uses of you/your with concrete subjects, per the "concrete subjects: teams, operators, signers, maintainers, responders, stewards" rule in docs/pages/contribute/style-and-terminology.mdx. Pages should not assume an individual reader rather than an organization. The overview heading "What a policy engine gives you" becomes "What a policy engine provides"; no page links to the old anchor. Claude-Session: https://claude.ai/code/session_01CPQ1FcHGiBKWPd8waT7uGx --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
…607) Add account-management guides and community-management framework pages for Session, Matrix, and SimpleX, following the two-layer structure already used for Discord, Telegram, and X. Settings paths and platform behaviours are sourced from vendor documentation and linked under Further reading on each page. Closes #599
…tors (#609) * docs(wallet-security): add dry-run recovery check * Add contributor * Update attribution list --------- Co-authored-by: Sara Russo <sararusso984@gmail.com> Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* Add OpenChainBench * Update OpenChainBench section with warning and details Added a warning note about the OpenChainBench project and provided a detailed description of its features and capabilities. --------- Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com>
* docs: clarify Telegram Mini App secret handling Add explicit credential and wallet-secret boundaries plus independent route verification. * docs: add Pointify contributor metadata Register public GitHub-only contributor metadata required for attribution. * Update attribution list * docs: narrow Telegram Mini App secret guidance --------- Co-authored-by: Sara Russo <sararusso984@gmail.com>
* Add roles requirements to contributing guides + sync root level contributing file + small fix in contributing sync script * Update "judgment" in CONTRIBUTING.md * Update "judgment" in contributing.mdx
…What this framework covers" (#615)
Deploying frameworks with
|
| Latest commit: |
45dc95c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8394fc97.frameworks-573.pages.dev |
| Branch Preview URL: | https://chore-spotlight-zone.frameworks-573.pages.dev |
|
Hi @scode2277, Following typos were found in the pull request:
ℹ️ Here's how to fix them:
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
mattaereal
approved these changes
Aug 31, 2026
5 of 9 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Monthly main update
Type of change
If applicable
vocs.config.tswith thedev: trueparameterStuck on anything? Just write it here and we're happy to help.