Glossary

Category

A technology grouping (e.g. "AWS", "Node.js", "React") used to organise components and deprecation data.

Component

A specific software library, SDK, service, or runtime tracked by deprec8. Examples: "AWS Lambda Node.js 16 Runtime", "React 17", "Python 3.8".

Deprecation

A formal announcement that a component will be discontinued, removed, or no longer supported after a specific date.

Deprecation Milestone

A specific stage in the deprecation lifecycle. Milestones progress through:

• Announced — the deprecation has been officially communicated
• Creation Blocked — new resources or installations can no longer be created
• Update Blocked — existing resources can no longer receive updates
• Fully Deprecated — the component is completely end-of-life

Manifest

A dependency declaration file used by package managers (e.g. package.json, pyproject.toml). deprec8 parses these to automatically identify project dependencies.

Organization

A shared workspace for team collaboration. Organizations can contain multiple projects and members with different permission levels.

Project

A logical grouping of dependencies within deprec8, typically representing a single deployable service or application.

Source

An external webpage, API, or feed that deprec8 monitors for deprecation announcements.

Urgency

A calculated priority level based on the time remaining until a deprecation takes effect:

• Critical — within 30 days
• Important — within 90 days
• Planned — within 6 months
• Future — more than 6 months away