Skip to content

Docs: add SECURITY.md and CONTRIBUTING.md - #256

Merged
tae898 merged 1 commit into
mainfrom
docs/security-and-contributing
Nov 5, 2026
Merged

tae898 merged 1 commit into
mainfrom
docs/security-and-contributing

Conversation

@tae898

@tae898 tae898 commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #255

Adds SECURITY.md and CONTRIBUTING.md, modelled on the files of ArcadeData/arcadedb. Nothing else changes.

SECURITY.md keeps upstream's structure (reporting, what to include, supported versions, my response, disclosure and credit, scope). Reports go through GitHub's private vulnerability reporting of this repository, never a public issue. A vulnerability in the engine itself (server, SQL, wire protocols, storage) goes to the private advisories of ArcadeData/arcadedb, as its SECURITY.md says. The supported version is the latest release of arcadedb and arcadedb-jvm, with the A.B.C, A.B.C.devN and A.B.C.postN numbering explained and linked to release.adoc. Upstream promises acknowledgement within 3 business days, an assessment within 10 and updates every 14; this file promises no times, because this repository has not agreed on any.

CONTRIBUTING.md is short and links to docs/ instead of repeating it: the licence, where a bug belongs (engine bugs go upstream), setup with uv only, build and test of both packages, test rules, pre-commit and Bandit, the issue, branch and Closes #N workflow, the timed A/B for performance changes, docs, and releases.

Assumption for maintainers: the security policy assumes private vulnerability reporting is enabled for this repository. That is a repository setting (Settings, Code security, Private vulnerability reporting) that a maintainer turns on; this PR does not change it. Until it is on, the "Report a vulnerability" link in SECURITY.md has nothing behind it.

Note on repository setup: this repository is not a uv project (pyproject.toml sets managed = false), so CONTRIBUTING.md does not say uv sync. It uses uv run --no-project --with "$W[test]" python -m pytest, as CLAUDE.md does. It also mentions the pull request template (.github/pull_request_template.md) and uvx pre-commit run --files <changed files>, which come from #252; merge #252 first, or reword that one paragraph if #252 changes.

How it was checked:

  • uvx pre-commit run --files SECURITY.md CONTRIBUTING.md run twice: nothing reformatted, the hooks that apply passed (the others had no files to check).
  • A search for pip install and the em dash over both files finds nothing.
  • All 12 relative links resolve to files in the checkout.
  • Each command in CONTRIBUTING.md (scripts/build.sh, ARCADEDB_TAG, --reinstall-package arcadedb-jvm, the uv run --no-project test lines, Bandit, the Antora build, build-image.sh, build_wheel.py --lib-dir, the parity suite step) was found with grep in README.md, CLAUDE.md, a workflow or a script of this repository.
  • Nothing was built or run: no Docker, Java or test suite.

🤖 Generated with Claude Code

SECURITY.md: private reporting through GitHub's private vulnerability reporting, a split between bindings and engine reports (engine goes to the ArcadeData/arcadedb advisories), supported versions and the A.B.C, A.B.C.devN, A.B.C.postN numbering, what to include, what happens next. Structure and tone follow the upstream file; no response times are promised.

CONTRIBUTING.md: licence, where a bug belongs, setup with uv only (the repository is not a uv project, so tests run from the built wheel with uv run --no-project), build and test of arcadedb-jvm and arcadedb (native) as the docs and workflows do, pre-commit and Bandit, workflow, timed A/B for performance changes, docs, releases. Links to docs/ pages instead of repeating them.

Closes #255

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tae898 tae898 added the documentation Improvements or additions to documentation label Nov 5, 2026
@tae898
tae898 merged commit 3487726 into main Nov 5, 2026
28 checks passed
@tae898
tae898 deleted the docs/security-and-contributing branch November 5, 2026 02:15
@tae898 tae898 added this to the 26.11.1 milestone Nov 5, 2026
tae898 added a commit that referenced this pull request Nov 5, 2026
…write) (#260)

The workflow from #252 failed on the merges of #252 and #256 with 403 Resource not accessible by integration when it set the pull request's milestone; issues: write covers issues only. The workflow still checks out no pull request code (pull_request_target), so the wider token stays safe.

Closes #259

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add SECURITY.md and CONTRIBUTING.md

1 participant