speckit-version-guard-validate

You can validate API compatibility by scanning newly modified source files against Compatibility Rules. This process detects version-incompatible API patterns based on your project's locked dependencies without blocking the workflow.

Static API compatibility scanning parses mandatory constraint rules and reviews changed source files to identify mismatched API patterns. It relies on a version-guard report but applies an in-memory fallback when disk artifacts are missing.

Version guard validation does not block your workflow. It outputs advisory findings that highlight incompatible API patterns and surfaces critical CVEs from Known Issues, allowing reviewers to assess risk without halting the pipeline.

Yes, you can scan TypeScript and JavaScript files for dependency locking issues. The validation applies to source files within your project, reading the feature directory to compare changed code against locked dependency versions.

If the version-guard report artifact is missing, the code validation uses an in-memory fallback to continue scanning. This ensures the post-implementation compatibility check still runs and surfaces advisory findings for your changed files.

You need to run compatibility checks after generating new code to prevent broken builds. Scanning modified files ensures newly introduced API patterns do not conflict with the project's locked dependency versions or known security issues.