docs(security): refresh policy and link published advisories - #375
Merged
Conversation
The supported-versions section still said "released and at v1.0.0" and
listed all of `1.x` as supported, which had drifted two minor releases.
It is now stated as a line ("1.2.x (current)") rather than a pinned
patch number, so it does not go stale on the next release.
Also:
- Point readers at /security/advisories, and tell them to read the
affected range on the advisory rather than comparing version numbers.
- Add a threat-model bullet for ingested documents. The loopback-only
default covers who can call the API, but filenames, metadata, and
content arriving from elsewhere are untrusted regardless of how the
API is reached.
- Note that reporters are credited in the advisory as well as the
release notes, which is what we do in practice.
Reporting stays email-only; GitHub private vulnerability reporting is
deliberately left disabled so the documented 5-business-day response
runs through one monitored inbox.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
dani1005
changed the title
cyfyifanchen
approved these changes
Jul 30, 2026
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.
Summary
SECURITY.mdhad drifted: the supported-versions section still read "EverOS isreleased and at v1.0.0 (stable)" and listed all of
1.xas supported, two minorreleases behind. This refreshes it and fills two gaps that
GHSA-grm3-hcqf-hm28
made visible.
1.2.x (current))rather than a pinned patch number, so the section does not go stale on the
next release — which is how the old text ended up two minors behind.
/security/advisories,with a note to read the affected range on the advisory rather than comparing
version numbers. Ranges are not always a simple "everything below X".
existing first bullet covers who can call the API (loopback-only by
default). It does not cover the case where the caller is trusted but the
filenames, metadata, and content it forwards are not — which is the shape of
the traversal fixed in 1.2.1.
what we actually do.
Reporting stays email-only. GitHub private vulnerability reporting is
deliberately left disabled: the documented 5-business-day acknowledgement is
easier to honour through one monitored inbox than through GitHub notifications
on this repo.
Area
Verification
Checklist
main..envfiles, dependency folders, or generated output.Notes for Reviewers
The supported-versions table is a policy statement, so it is worth an
explicit look: it now says
1.1.xand older receive no backports. That matchesthe previous wording ("applied to the latest release line only") and the current
reality that this repository has no maintenance branches — only
main. If theintent is to keep patching a
1.1.xline, this table needs to say so instead.By submitting this pull request, I agree that my contribution is licensed under
the Apache License 2.0.