Open-Source Version Maintenance Rating via ML Package Clustering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application management systems lack effective methods to assess the reliability and upkeep of open-source packages and versions, leading to potential vulnerabilities and maintenance issues.

Innovation Solution

A predictive machine learning model trained on labeled datasets generates ratings of staleness or vibrancy for open-source packages and versions, using package-basis and version-basis clustering to identify undermaintained or deprecated components and facilitate updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional application management systems are used to monitor open-source packages, then system simplicity is maintained, but the ability to assess reliability and detect undermaintained packages is insufficient

Engineering Contradiction:
Improveassessment of open-source package reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces machine learning models as intermediary components between the application management system and open-source package repositories. These models analyze package metadata, version histories, and community engagement metrics to generate reliability assessments, enabling the system to detect undermaintained packages without requiring direct complex analysis of each package's entire codebase and history.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary analysis by pre-processing and storing key package attributes, version information, and maintenance indicators in structured formats. This preliminary action enables rapid reliability assessment when packages are added or updated, avoiding the need for complex real-time analysis while maintaining high reliability detection capability.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If comprehensive analysis of all open-source package attributes is performed, then detection accuracy improves, but processing time increases

Engineering Contradiction:
Improvedetection accuracy of undermaintained packagesVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent segments the analysis into distinct components: package metadata analysis, version history analysis, and community engagement analysis. Each segment is processed by specialized machine learning models that focus on specific aspects, enabling comprehensive detection accuracy while processing only relevant features for each package type rather than analyzing all possible attributes uniformly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial analysis by focusing on the most critical maintenance indicators such as last update timestamp, version release frequency, and active issue counts. Rather than analyzing every possible package attribute, the system concentrates computational resources on the subset of features that most strongly correlate with package maintenance status, achieving high detection accuracy with reduced processing time.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12493462B2Systems and methods for detecting usage of undermaintained open-source packages and versions
Publication Date: 2025.12.09 MOJO TECH SAS
  • US12493462B2 patent drawing
  • US12493462B2 patent drawing
  • US12493462B2 patent drawing

AI summary

Various embodiments of the present disclosure provide methods, apparatus, systems, computing devices, computing entities, and/or the like for identifying stale or vibrant open-source packages by training a predictive machine learning model with a labeled dataset, wherein the labeled dataset is created by generating package-basis features and version-basis features based on repository data, generating package-basis clusters based on the package-basis features, generating version-basis clusters based on the version-basis features, and generating labels for the labeled dataset based on the package-basis clusters and the version-basis clusters.