Suspected vulnerability? Please do not open a public issue. Use GitHub's private vulnerability reporting.
Security fixes are provided for the latest 0.3.x release. Users on 0.2.x or older should upgrade before reporting an issue that may already be resolved.
The default offline profile exposes no HTTP tools. Repository reads are constrained
to the active repository after canonical-path and symlink/junction checks. The stricter
pinned profile also removes repository switching and cross-repository graph reads.
The MIT weavatrix 0.3 package contains no outbound HTTP implementation. Cloud and
licensed self-hosted transport lives in the separately installed weavatrix-online
product. It performs endpoint capability negotiation and requires an exact preview confirmation
before sync. The graph-sync contract excludes source bodies, snippets, absolute host paths,
environment values, credentials and Git remotes; unknown payload fields are discarded.
Core has no application-source write path. It stores derived analysis caches outside the
repository; explicit architecture approval may create .weavatrix/architecture.json
only after preview and token confirmation. The separately installed Apache-2.0
weavatrix-refactor package can edit source only when its profile, environment gate
and single-use plan token all authorize the exact reviewed plan. It verifies hashes and expected
text, applies atomically and creates an external rollback bundle.
Process isolation, optional test execution, payload limits and reporting details are documented in the repository's complete security policy. See also the privacy policy and license.