Skip to content

GitHub Rulesets

Home · Top · Table of Contents

Table of Contents

Kevin K. Le (LinkedIn) — Founder, Founding Engineer, and Current Lead Engineer; Software Engineer at the Oregon Blockchain Group, University of Oregon.

Kellen Snider — Founding Engineer; Software Engineer at the Oregon Blockchain Group, University of Oregon. His vision, ideas, and dedication during TrustLedger's Ethereum development were invaluable to the codebase we build on today.

See CREDITS.md.

GitHub rulesets are the server-side backstop for mistakes that local Git hooks cannot stop, including git commit --no-verify, direct CLI pushes, and forced push attempts.

Sensitive File Protection

Home · Top · Table of Contents

The importable ruleset template lives at:

.github/rulesets/protect-sensitive-files.json

It blocks pushes that try to add or modify high-risk paths such as:

  • .env and .env.*, except example files through local guard policy.
  • target/deploy/*.json.
  • *keypair*.json and *-keypair.json.
  • Secret JSON/YAML files.
  • Private-key-looking filenames.

The template also enables secret-scanning push protection where the repository plan supports it. Repository admins should import or recreate this ruleset in GitHub Settings -> Rules -> Rulesets and keep enforcement set to active.

Required Repository Settings

Home · Top · Table of Contents

Enable these GitHub settings:

  • Secret scanning.
  • Push protection.
  • Push ruleset with file path restrictions from .github/rulesets/protect-sensitive-files.json.
  • No bypass actors for the sensitive-file ruleset unless an emergency breakglass process is documented separately.

GitHub can reject protected file paths server-side. That is the closest practical answer to "never under any circumstances," because local hooks can always be bypassed by a user with their own Git client.

Local And CI Backstops

Home · Top · Table of Contents

The repository also runs:

npm run secrets:check

This guard checks tracked and staged files for forbidden paths and common secret content. It runs in pre-commit, pre-push, npm run quality, and CI.

Authors and Contributors

Home · Top · Table of Contents

  • Kevin K. Le — Founder, Founding Engineer, and Current Lead Engineer (LinkedIn)
  • Kellen Snider — Founding Engineer (LinkedIn)

See CREDITS.md for the complete acknowledgement list.

Home · Top · Table of Contents

This document is part of TrustLedger, an open-source decentralized escrow and arbitration protocol. Use of this software and documentation is subject to the Terms and Conditions, Privacy Policy, and Risk Disclosure. See LEGAL.md for the full compliance and licensing overview.