Internet-Draft Repository Availability Reporting November 2026
Arsentev Expires 20 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-arsentev-repository-availability-reporting-00
Published:
Intended Status:
Informational
Expires:
Author:
E. Arsentev
Independent

Reporting the Availability of Referenced Software and Model Repositories

Abstract

Papers, catalogues, model cards and tool lists point to code and model repositories by URL. Such repositories can be deleted, made private, blocked or simply stop changing, and reports of "link rot" or "project survival" often mix these different events into one number. This document defines how to classify each observation of a referenced repository, when a repository counts as unavailable, how to report inactivity separately from unavailability, and a small JSON report object. It also recommends citing a persistent identifier or an archived copy next to the repository URL.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 20 May 2027.

▲

Table of Contents

1. Introduction

Lists of software and models, including curated catalogues of AI tools, cite repositories on hosting platforms such as GitHub and Hugging Face by URL. A URL can stop resolving for several reasons, and a project can remain reachable while nobody changes it any more.

Platforms answer a missing repository in different ways. A platform may return 404 (Section 15.5.5 of [RFC9110]) for one missing repository and 401 (Section 15.5.2 of [RFC9110]) for another. The status 451 ([RFC7725]) is used when access is blocked for legal reasons. Single checks are noisy, because a request can fail for reasons unrelated to the repository.

The goal of this document is to make the definition behind every reported availability number explicit, so that numbers from different studies can be compared. This document does not define how to archive repositories, does not rank projects, and does not say which projects should be cited.

2. Conventions and Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

This document uses the following terms:

referenced repository:
a repository URL that appears in a list, catalogue or document being studied.
selection date:
the date the repository entered the list being studied.
snapshot:
one check of all referenced repositories made at one time.
horizon:
a number of weeks after the selection date at which availability is reported.

3. Classifying Observations

Each snapshot records, for every referenced repository, one of the following states:

available:
the repository page or API answered with success.
missing:
the platform answered with a status the report lists as "repository missing" for that platform (for example 404 or 451 on one platform, 401 or 404 on another).
error:
any other failure, such as a timeout or a server error. An error is not evidence that the repository is gone.

The report MUST list, per platform, which status codes it treats as missing. A repository MUST NOT be counted as unavailable after a single missing observation. The report MUST state how many consecutive missing snapshots it requires.

A repository that becomes available again after being counted as unavailable is reported as a return. It is not deleted from the data.

4. Inactivity Is a Separate Count

Inactivity means no change to the repository for a stated number of days, for example no push for 90 days. Inactivity and archiving by the owner are reported separately from unavailability.

A composite count that adds inactivity to unavailability MUST be labelled as composite.

A fixed inactivity threshold produces a step in a composite curve once observed projects pass that threshold. Such a step is a property of the rule, not evidence that projects disappeared.

5. Reporting over Time

Availability is reported at stated horizons counted from each repository's selection date, not from the first snapshot.

The report gives the estimator used (for example Kaplan-Meier) and the number of repositories still under observation at each horizon. The report SHOULD NOT report horizons where very few repositories remain under observation.

The report states the selection rule of the list, because a result about one list does not describe a whole platform.

6. Report Object

The results of a study can be carried in a JSON object ([RFC8259]). The object carries the observation window, the per-platform missing status codes, the consecutive-snapshot rule, and per-horizon availability with the number of repositories under observation. The example in the appendix uses illustrative numbers, not measurements.

The report is a JSON object [RFC8259] with the following members.

list
Object, REQUIRED, with members "name" (string naming the list or catalogue studied), "selection_rule" (string describing how entries entered the list) and "entries" (non-negative integer).
window
Object, REQUIRED, with members "first_snapshot" and "last_snapshot" (each a full-date as defined in [RFC3339]) and "snapshots" (non-negative integer).
platforms
Array, REQUIRED, one object per hosting platform, with members "platform" (string), "observed" (non-negative integer) and "missing_status" (array of integer HTTP status codes treated as missing).
consecutive_missing
Integer of at least 2, REQUIRED. Number of consecutive missing snapshots after which a repository is counted as unavailable.
unavailable
Non-negative integer, REQUIRED. Repositories counted as unavailable at least once.
returned
Non-negative integer, REQUIRED. Repositories counted as unavailable that were later available again.
inactive
Object, OPTIONAL, with members "rule" (string, for example "no push for 90 days") and "count" (non-negative integer). Never added to "unavailable".
estimator
String, REQUIRED, for example "kaplan-meier".
horizons
Array, REQUIRED, one object per reported horizon, with members "weeks" (positive integer, counted from each repository's selection date), "available" (number between 0 and 1) and "at_risk" (non-negative integer, repositories still under observation at that horizon).

Members not defined here MAY be added; consumers MUST ignore members they do not understand.

7. Citing Repositories

Documents that cite a repository SHOULD also give a persistent identifier (for example a DOI of an archived release) or the URI of an archived copy, such as a Memento ([RFC7089]), next to the repository URL.

The repository URL alone tells a later reader where the project was, not what was cited.

8. Operational Experience

One curated radar of AI tools selected 757 entries between 11 June and 31 October 2026. 733 GitHub and Hugging Face projects were observed in 50 daily snapshots from 12 September to 31 October 2026. The metric was fixed on 5 October 2026, before analysis.

Unavailability was defined as 404 or 451 on GitHub and 401 or 404 on Hugging Face, two snapshots in a row. 23 projects became unavailable and 5 of them later came back.

Kaplan-Meier availability was 96.7% at week 4, 94.6% at week 8 and 93.0% at week 12 after selection, roughly one project in 14 lost by week 12.

Inactivity was more common than removal: 67 projects had no push for 90 days, against 23 that became unavailable. A composite curve that included inactivity dropped sharply after week 12, and that drop came from the 90-day rule.

These numbers come from one radar with one selection rule and do not describe GitHub or Hugging Face as a whole. The study is published with DOI 10.5281/zenodo.24101933 [SURVIVAL].

9. Security Considerations

Repeated automated checks of many repositories can trigger platform rate limits. Checks SHOULD respect the platform's published limits.

A repository URL that resolves again after a gap may now hold different content under the same name. Reports that record returns SHOULD note that content was not compared unless it was.

10. Privacy Considerations

The report carries counts and status codes only. It SHOULD NOT name individual repository owners.

Small counts per platform or per month can still point to a specific project. Operators SHOULD consider this before publishing per-cell numbers.

11. IANA Considerations

This document has no IANA actions.

12. References

12.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC3339]
Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, , <https://www.rfc-editor.org/info/rfc3339>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[RFC8259]
Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, DOI 10.17487/RFC8259, , <https://www.rfc-editor.org/info/rfc8259>.
[RFC9110]
Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., "HTTP Semantics", STD 97, RFC 9110, DOI 10.17487/RFC9110, , <https://www.rfc-editor.org/info/rfc9110>.

12.2. Informative References

[RFC7089]
Van de Sompel, H., Nelson, M., and R. Sanderson, "HTTP Framework for Time-Based Access to Resource States -- Memento", RFC 7089, DOI 10.17487/RFC7089, , <https://www.rfc-editor.org/info/rfc7089>.
[RFC7725]
Bray, T., "An HTTP Status Code to Report Legal Obstacles", RFC 7725, DOI 10.17487/RFC7725, , <https://www.rfc-editor.org/info/rfc7725>.
[SURVIVAL]
Arsentev, E., "How Long Do Trending AI Projects Stay Available and Maintained? Survival of 733 GitHub and Hugging Face Projects Picked by a Weekly Radar (June-October 2026)", Zenodo, DOI 10.5281/zenodo.24101933, , <https://doi.org/10.5281/zenodo.24101933>.

Appendix A. Example Report

The numbers in this example are illustrative and are not measurements.

{
  "list": {"name": "example-tool-catalogue",
           "selection_rule": "weekly editorial pick",
           "entries": 500},
  "window": {"first_snapshot": "2026-09-01",
             "last_snapshot": "2026-10-31",
             "snapshots": 61},
  "platforms": [
    {"platform": "example-code-host", "observed": 400,
     "missing_status": [404, 451]},
    {"platform": "example-model-host", "observed": 100,
     "missing_status": [401, 404]}
  ],
  "consecutive_missing": 2,
  "unavailable": 20,
  "returned": 4,
  "inactive": {"rule": "no push for 90 days", "count": 50},
  "estimator": "kaplan-meier",
  "horizons": [
    {"weeks": 4,  "available": 0.98, "at_risk": 450},
    {"weeks": 8,  "available": 0.96, "at_risk": 300}
  ]
}

In this example 20 repositories were missing in two snapshots in a row and 4 of them later answered again. The 50 inactive repositories are reported in their own member and are not part of the availability figures.

Author's Address

Evgenii Arsentev
Independent