Struct EcosystemValidator 

pub struct EcosystemValidator { /* private fields */ }

Comprehensive ecosystem validator for production environments

Implementations

impl EcosystemValidator

pub fn new() -> CoreResult<Self>

Create new ecosystem validator

pub fn global() -> CoreResult<Arc<Self>>

Get global validator instance

pub fn register_module(&self, module: ModuleInfo) -> CoreResult<()>

Register a module in the ecosystem

pub fn validate_ecosystem(&self) -> CoreResult<EcosystemValidationResult>

Validate entire ecosystem compatibility

pub fn validate_module( &self, modulename: &str, ) -> CoreResult<ModuleValidationResult>

Validate specific module compatibility with ecosystem

pub fn updatepolicies(&self, newpolicies: ValidationPolicies) -> CoreResult<()>

Update validation policies

pub fn get_ecosystem_health(&self) -> CoreResult<EcosystemHealth>

Get ecosystem health summary

pub fn has_circular_dependency( &self, registry: &ModuleRegistry, module: &str, dependency: &str, ) -> bool

Real cycle detection: would registering dependency as a dependency of module create a circular dependency chain?

This performs a DFS over the existing declared dependency edges starting at dependency: if module is reachable from dependency, then adding the edge module -> dependency would close a cycle back to module. A direct self-dependency (module == dependency) is trivially a cycle.

(A generic executable crate::distributed::task_graph::TaskGraph exists elsewhere in this crate, but it is oriented around scheduling closures for execution; a plain reachability walk over the declarative ModuleRegistry data is simpler and does not require wrapping module metadata in executable tasks.)

pub fn areversions_compatible( &self, version_a: &Version, version_b: &Version, policies: &ValidationPolicies, ) -> bool

Real semver-based pairwise version compatibility: under strict_version_matching the versions must match exactly, otherwise modules sharing a major version are considered compatible (the standard semver contract for a stable release; see crate::apiversioning::Version::is_compatible_with for the single-version analogue used elsewhere in this crate).

pub fn are_apis_compatible(&self, api_a: &ApiSurface, apib: &ApiSurface) -> bool

Real API-presence check: flags a genuine symbol conflict, i.e. two modules independently declaring a public API with the same name but a different signature. Modules that share no API names, or share names with identical signatures, are compatible.

pub fn are_features_compatible( &self, features_a: &[String], featuresb: &[String], policies: &ValidationPolicies, ) -> bool

Real feature-compatibility check: neither module may enable a feature that ecosystem policy has blacklisted as incompatible (the same incompatible_features policy enforced per-module by the private is_feature_compatible method, applied here to a module pair).

pub fn check_api_stability( &self, previous: Option<&ApiSurface>, current: &ApiSurface, ) -> ApiStabilityCheck

Real API-stability check comparing current against previous (if any version was previously registered for this module): detects removed public APIs and changed signatures, both breaking changes. A module with no prior recorded version is trivially stable (there is nothing to have broken yet).

pub fn is_api_properly_versioned(&self, apisurface: &ApiSurface) -> bool

Real versioning-compliance check: every public API must carry a since_version annotation.

pub fn has_known_vulnerabilities( &self, _dependency_name: &str, ) -> VulnerabilityStatus

Vulnerability lookup for a dependency by name.

This crate has no vulnerability-advisory database (e.g. a RustSec feed) integrated, and none of [workspace.dependencies] provides one; adding a live/networked lookup here would also make ecosystem validation non-hermetic. Rather than fabricate a “no known vulnerabilities” verdict, this honestly reports that the dependency was never checked. See SecurityValidationResult::unchecked_dependencies.

Trait Implementations

impl Debug for EcosystemValidator

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.