## Summary
Dependabot security update for the repository-root npm tree. Closes
seven open
Dependabot alerts, all high severity:
| Package | From | To | Advisories |
|---|---|---|---|
| fast-uri | 3.1.3 | 3.1.7 | GHSA-v2hh-gcrm-f6hx, GHSA-7p8r-x3mc-p8w7,
GHSA-5jgf-p345-68v8, GHSA-fph4-wmhf-6fwf, GHSA-f65p-4m7j-42xc,
GHSA-jqff-g426-hqxp (host confusion and SSRF in URI parsing) |
| js-yaml | 4.3.0 | 4.3.2 | GHSA-5p4m-2wfm-xmqj, GHSA-2883-xcg3-v3hh
(quadratic and unbounded CPU use in !!omap and merge-key resolution) |
Both are development dependencies, and this npm tree is not shipped: its
only
direct dependency is `@commitlint/cli`, which runs the commit-message
gate in
CI. `fast-uri` reaches us through `ajv`, which resolves `$ref` URIs
inside
commitlint's own schema; `js-yaml` reaches us through `cosmiconfig`,
which loads
config files, and this repo's config is `commitlint.config.cjs`, not
YAML.
Neither parser is fed anything from a pull request, so the exposure here
is
alert hygiene rather than a reachable path -- which is also why this is
the
cheapest of the four to take.
This description replaces Dependabot's default. That one quotes upstream
release
notes verbatim, so it carries emoji and em-dashes, and the repository
lints the
PR body as ASCII because the squash merge uses it as the commit body.
## Type
- [ ] Fix
- [ ] Feature
- [ ] Docs
- [x] CI / tooling
- [ ] Refactor
- [ ] Other
## Verification
The diff is six lines of `package-lock.json`. Reachability was read off
the
lockfile rather than assumed:
```
$ python3 -c "...load package-lock.json..."
node_modules/fast-uri dev=True required by: node_modules/ajv
node_modules/js-yaml dev=True required by: node_modules/cosmiconfig
non-dev packages in this lock: 0 (77 packages total)
```
CI must be green on this branch before it merges; the checks that failed
before
the rebase were stale runs from 2026-09-11 plus the two commit-lint
gates, which
`ci(*): accept the deps-dev scope and pin dependabot's commit prefix`
(#441)
fixed on main.
- [ ] Relevant tests pass locally
- [ ] Relevant lint / type checks pass locally
- [ ] User-facing docs or screenshots are updated when needed
## Risk
No runtime behaviour changes: nothing in this lockfile is installed by
users or
packaged into the wheel. The risk of taking it is that commitlint itself
breaks
in CI, which the commit-lint jobs on this PR exercise directly. Rollback
is to
revert the commit.
- [x] Security impact considered
- [x] Backward compatibility considered
- [x] Rollback path is clear for risky changes
## Related Issues
N/A. Closes seven Dependabot alerts on `package-lock.json`.
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
## Summary
- switch project metadata and license text to Apache-2.0 while retaining
upstream notices
- add public-ready community files: issue templates, SECURITY,
CONTRIBUTING, CODE_OF_CONDUCT, Dependabot, and a stricter PR template
- align README license copy with the public launch posture
## Repository settings updated via GitHub API
- squash-only merge enabled; merge commit and rebase merge disabled
- delete branch on merge and update branch enabled
- Discussions enabled; Projects and Wiki disabled
- Actions default workflow permissions set to read-only and PR
self-approval disabled
- description and homepage updated for Raven
## Verification
- npm ci --ignore-scripts --no-audit --no-fund (root)
- npm ci --ignore-scripts --no-audit --no-fund (ui-tui)
- npm ci --ignore-scripts --no-audit --no-fund (bridge)
- npx --no-install commitlint --from origin/main --to HEAD --config
commitlint.config.cjs
- PYTHONPATH=. python3 scripts/check_commit_messages.py
origin/main..HEAD
- uv run pre-commit run --from-ref origin/main --to-ref HEAD
- git diff --check origin/main...HEAD
## Notes
- GitHub branch protection/rulesets returned 403 while the repository is
private on the current plan. Enable required checks after making the
repository public.
- Auto-merge remained disabled after the API patch, likely due
repository/org availability or policy.
EverOS defaulted both its user-level config toml and its data root
(sqlite / lancedb / .index / ome.db) to a bare ~/.everos. Scope raven's
instance under ~/.everos/raven so config and data stay isolated from any
other EverOS consumer on the machine.
Add update_everos.configure_everos_env(): it sets EVEROS_CONFIG_FILE and
EVEROS_MEMORY__ROOT via setdefault (so an explicit operator override
still wins) before EverOS's @cache-d load_settings() first runs. The
everos backend factory and the understand_media tool factory call it as
the earliest raven-controlled EverOS entry points; _EVEROS_CONFIG now
derives from a single _EVEROS_BASE constant.
No data migration: existing ~/.everos data is left untouched and a fresh
~/.everos/raven is created lazily on first write/use.
Co-authored-by: Claude (claude-opus-4-8) <noreply@anthropic.com>