OSS Deprecation Prediction via ML Vector Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lack of predictability of end-of-life (EOL) for open-source software (OSS) poses significant challenges for developers and administrators, leading to crisis-driven development and increased technical risks.

Innovation Solution

An automated solution utilizing machine learning (ML) for metadata and code-commit analysis, combined with product maturity lifecycle analysis and predictive visualization, to predict the EOL of OSS by analyzing OSS indicia and metadata from open-source repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automated machine learning analysis is implemented to predict OSS end-of-life, then predictability of EOL is improved, but device complexity increases

Engineering Contradiction:
Improvepredictability of end-of-lifeVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the complex prediction task into multiple independent modules: data collection module that gathers OSS metadata and commit history, preprocessing module that cleans and normalizes data, feature extraction module that identifies relevant patterns, and prediction module that generates EOL forecasts. Each module handles a specific aspect of the analysis, making the overall complex system manageable and maintainable while achieving high predictability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary components including data normalization layers that standardize diverse OSS data formats, feature engineering intermediaries that transform raw metadata into meaningful indicators, and model interpretation layers that translate complex ML outputs into actionable predictions. These intermediaries bridge the gap between raw data and final predictions, reducing the apparent complexity for end users

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If comprehensive metadata and code-commit analysis is performed, then measurement precision of EOL prediction is improved, but loss of time increases

Engineering Contradiction:
Improveprediction accuracyVSAvoidanalysis time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system implements partial analysis by focusing on the most discriminative features and metadata fields that have the highest correlation with EOL outcomes. Rather than analyzing every single metadata field and commit uniformly, the model identifies and prioritizes key indicators such as commit frequency patterns, contributor retention metrics, and dependency update rates, achieving high prediction accuracy with reduced analysis time

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent applies preliminary data preprocessing and feature engineering steps that prepare data in advance for efficient processing. Historical OSS data is pre-cleaned, normalized, and transformed into meaningful features before the actual prediction occurs. This preliminary action reduces the computational burden during real-time prediction, enabling both high precision and fast analysis

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If timely prediction of OSS deprecation is achieved, then loss of time for transition planning is reduced, but device complexity increases

Engineering Contradiction:
Improvetransition preparation timeVSAvoidautomation system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system implements self-service capabilities where the automated prediction platform performs data collection, analysis, and prediction generation without requiring manual intervention. The system autonomously monitors OSS projects, automatically updates prediction models with new data, and generates timely alerts when deprecation is forecasted, reducing transition preparation time while managing complexity through automation rather than manual processes

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250036399A1Automated Open Source Deprecation Prediction
Publication Date: 2025.01.30 BANK OF AMERICA CORP
  • US20250036399A1 patent drawing
  • US20250036399A1 patent drawing
  • US20250036399A1 patent drawing

AI summary

A distributed, automated, open-source software (OSS) deprecation-prediction system/process is disclosed. OSS indicia/metadata is retrieved from repositories and stored in a master datastore. OSS metadata is extracted and normalized. Data typification is performed to create static data snapshots, which are stored in a static datastore and provided to a ML surface analytics module, a ML cluster analytics module, and a dynamic data store. ML surface analysis generates rolling time-series n-space vector maps. ML cluster analysis generates time-based cluster analysis data including includes clusters of interior, on-surface, and exterior data points, and a metric for cluster quality for self-reinforcement. An end-of-life (EOL) analytics module generates an EOL deprecation prediction for the OSS based on the dynamic data using ML technique for vectors trending toward the interior or exterior of multi-dimensional vector space.