Conversation
…t badges - .github/workflows/codeql.yml: security-and-quality query suite on push/PR + weekly cron, ignores vendored Saxon-JS, tests/, dist/ - .github/workflows/scorecard.yml: OpenSSF Scorecard weekly + push to main, publishes to api.scorecard.dev, uploads SARIF - .github/dependabot.yml: weekly npm devDeps and github-actions updates, grouped minor+patch - SECURITY.md: vulnerability reporting policy plus honest posture statement (no backend, no telemetry, zero runtime deps, GoatCounter disclosed) - README.md: 4 new badges (CodeQL, Scorecard, Dependabot, No Telemetry) and a Security section linking to SECURITY.md Repo settings (configured separately via API): branch protection on main with required e2e-tests check, secret scanning + push protection, Dependabot security updates and alerts.
Contributor
Deploying xsltdebugx with
|
| Latest commit: |
d7d18cc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://71921dbb.xsltdebugx.pages.dev |
| Branch Preview URL: | https://dev.xsltdebugx.pages.dev |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
Resolves two Dependabot alerts: - GHSA-fx2h-pf6j-xcff (high): vite server.fs.deny bypass on Windows alternate paths - GHSA-v6wh-96g9-6wx3 (medium): launch-editor NTLMv2 hash disclosure via UNC paths on Windows Both CVEs affect Vite's dev server on Windows only. This project uses Vite for the production build (`npm run build`), not as a live dev server (`npm run serve` runs http-server), so practical exposure is nil. Bumping anyway to clear the alerts and live up to the SECURITY.md "continuous scanning" claim. Lockfile-only change; declared range `^6.0.0` already permits 6.4.3. Verified: `npm run build` passes.
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
2 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
Adds four verifiable trust signals so users (especially security teams reviewing the tool for CPI work) can confirm the repo is safe without taking our word for it.
Changes
.github/workflows/codeql.ymlsecurity-and-qualityquery suite. Runs on every push, every PR, and weekly. Vendoredlib/SaxonJS2.js,tests/, anddist/are excluded so findings only target our code..github/workflows/scorecard.yml.github/dependabot.ymlSECURITY.mdREADME.mdWhy these four scanners
eval, etc. Most defensible claim for a vanilla-JS app.Repo settings already configured via API
main: PR required,e2e-testsmust pass, branch up-to-date, no force pushes, no deletionsNotes
main(Mondays 07:00 UTC) or a manualworkflow_dispatch.