awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
endoflife-date avatar

endoflife-date/endoflife.date

0
View on GitHub↗
3,153 stars·1,132 forks·Ruby·mit·24 viewsendoflife.date↗

Endoflife.date

This project is a product support database and software version metadata registry that tracks release and discontinuation timelines for software and consumer electronics hardware. It provides a programmatic software lifecycle API for retrieving end-of-life and support dates via JSON.

The project maps software products to standardized identifiers, including CPE, Repology, and PURL, to ensure cross-ecosystem identification. It also includes a runtime compatibility mapper that matches software versions to their minimum required compatible runtimes and dependencies.

The system transforms lifecycle data into RSS and iCalendar feeds for subscription-based notifications and calendar synchronization. Data is served via a static site and a flat-file JSON API.

Features

  • Support Status Tracking - Provides a comprehensive database for monitoring the support status and end-of-life timelines of software versions.
  • Lifecycle Support Monitors - Tracks software version lifecycles and support availability to help plan upgrades and security patches.
  • Versioned Metadata Tracking - Maintains a registry of standardized CPE and PURL identifiers linked to product version history.
  • Product Identifiers - Implements standardized CPE, Repology, and PURL identifiers to ensure consistent product mapping across ecosystems.
  • Static JSON Stores - Uses version-controlled JSON files as a static, read-only data store for all lifecycle metadata.
  • Product Support Databases - Maintains a comprehensive repository of release and discontinuation timelines for software and consumer electronics.
  • Software Lifecycle APIs - Provides a programmatic JSON interface for retrieving end-of-life and support dates for software and hardware.
  • Cross-Ecosystem Product Identifiers - Maps software products to standardized CPE, Repology, and PURL identifiers to ensure consistent cross-ecosystem identification.
  • Support Timeline Tracking - Monitors release and end-of-life dates for software and hardware to plan necessary upgrades.
  • Support Status Auditing - Uses standardized identifiers like CPE and PURL to verify the support status of specific software versions.
  • Metadata Integration APIs - Provides a programmatic JSON interface for integrating software lifecycle and support dates into external tools.
  • Calendar Integrations - Synchronizes software support and expiration dates with personal or team schedules via calendar feeds.
  • Calendar Feed Generation - Transforms raw lifecycle data into iCalendar and RSS feeds for external calendar synchronization.
  • Runtime Version Mappings - Maps software versions to their minimum required compatible runtimes to ensure environment stability.
  • Version and Compatibility Management - Matches software versions with compatible runtimes and framework versions to ensure stable environment configurations.
  • Version Compatibility Utilities - Provides structured metadata that links software releases to compatible runtime versions for dependency verification.
  • Hardware Lifecycle Tracking - Provides end-of-life dates and support timelines for consumer electronics and specialized hardware devices.
  • Runtime Version Compatibility - Matches software versions to their minimum required compatible runtimes and dependencies.
  • Lifecycle Calendar Feeds - Exports software end-of-life dates into calendar formats for visibility in schedules.
  • Lifecycle Notification Feeds - Offers RSS and iCalendar feeds to notify users of upcoming end-of-life events and support date changes.
  • Lifecycle Notifications - Exports software end-of-life dates in iCalendar format for synchronization with organizational calendars.

Star history

Star history chart for endoflife-date/endoflife.dateStar history chart for endoflife-date/endoflife.date

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Projects sharing features with Endoflife.date

These projects share indexed features with Endoflife.date. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • rust-lang/cargorust-lang avatar

    rust-lang/cargo

    14,624View on GitHub↗

    Cargo is the official build system and package manager for the Rust programming language. It provides a unified command-line interface that orchestrates the entire development lifecycle, including compiling source code, managing complex dependency graphs, running tests, and distributing packages through a centralized registry. By utilizing declarative manifest files, it ensures that builds remain reproducible and consistent across different environments. The tool distinguishes itself through its deep integration with the Rust compiler and its sophisticated approach to project management. It f

    Rustcargopackage-managerrust
    View on GitHub↗14,624
  • hotheadhacker/no-as-a-servicehotheadhacker avatar

    hotheadhacker/no-as-a-service

    6,153View on GitHub↗

    No-as-a-Service is a lightweight, self-hosted API that returns a random humorous rejection reason as a JSON object through a single GET endpoint. It serves pre-defined rejection reasons from a static JSON array without any database, external storage, or third-party dependencies, using only Node.js built-in modules for its zero-dependency HTTP server. The API processes each request independently with no session state, caching, or persistent connections, making it a stateless REST endpoint. Its rejection reasons are stored in a simple, human-readable JSON configuration file that can be edited w

    JavaScriptapiexpressjsjson
    View on GitHub↗6,153
  • deepsourcecorp/good-first-issueDeepSourceCorp avatar

    DeepSourceCorp/good-first-issue

    3,370View on GitHub↗

    This project is a developer onboarding tool and GitHub issue discovery portal. It serves as a curated directory and contribution guide designed to match new programmers with beginner-friendly open source tasks based on their technical skills and experience level. The platform operates as a static project directory, using a serverless catalog of repositories stored in JSON files. It provides the ability to filter tasks by programming language and difficulty, enabling users to identify approachable starting points in active software projects. The system includes capabilities for repository cur

    Pythoncontributions-welcomegood-first-issueopen-source
    View on GitHub↗3,370
  • cat-milk/anime-girls-holding-programming-bookscat-milk avatar

    cat-milk/Anime-Girls-Holding-Programming-Books

    22,312View on GitHub↗

    This project is a themed technical art collection and visual archive of stylized illustrations depicting computer science literature. It serves as a technical book illustration gallery that pairs anime-style characters with specific programming and technical textbooks. The repository functions as a static technical asset library, utilizing a JSON-driven image gallery to map visual assets to their corresponding metadata. This structured approach allows for the sourcing of theme-consistent artwork for use in developer blogs, presentations, and technical documentation. The system employs a resp

    anime
    View on GitHub↗22,312
Compare all 30 related projects→

Frequently asked questions

What does endoflife-date/endoflife.date do?

This project is a product support database and software version metadata registry that tracks release and discontinuation timelines for software and consumer electronics hardware. It provides a programmatic software lifecycle API for retrieving end-of-life and support dates via JSON.

What are the main features of endoflife-date/endoflife.date?

The main features of endoflife-date/endoflife.date are: Support Status Tracking, Lifecycle Support Monitors, Versioned Metadata Tracking, Product Identifiers, Static JSON Stores, Product Support Databases, Software Lifecycle APIs, Cross-Ecosystem Product Identifiers.

Which projects share features with endoflife-date/endoflife.date?

Projects with overlapping indexed features include: rust-lang/cargo — Cargo is the official build system and package manager for the Rust programming language. It provides a unified… hotheadhacker/no-as-a-service — No-as-a-Service is a lightweight, self-hosted API that returns a random humorous rejection reason as a JSON object… killbill/killbill — Kill Bill is a subscription billing platform and usage-based billing engine designed to manage recurring invoicing and… deepsourcecorp/good-first-issue — This project is a developer onboarding tool and GitHub issue discovery portal. It serves as a curated directory and… cat-milk/anime-girls-holding-programming-books — This project is a themed technical art collection and visual archive of stylized illustrations depicting computer… pheralb/svgl.