Is the iamazeem/substitute-action GitHub Action still maintained?
alive — observed 2026-08-31
As of 2026-08-31, the GitHub Action github.com/iamazeem/substitute-action is recorded alive: the repository's last public activity was within 180 days of the observation. Last public activity 2026-06-22. 2 dated observation(s) on record since 2026-08-02; 8 stars and 1 forks read 2026-08-02.
github.com/iamazeem/substitute-action is recorded as alive in the lastseen.dev component-maintenance dataset as of 2026-08-31. Definition: the repository's last public activity was within 180 days of the observation. Adoption at the latest read: 8 stars, 1 forks (read 2026-08-02). The page carries 2 dated observations from 2026-08-02 onward. The recorded state did not change across the series. Method: read from the public GitHub repository metadata and star/fork counts (authoritative). This is a dated factual observation series about one GitHub Action, not advice about any named party.
API: this register also serves a free JSON API — see /api/v1/docs. (Per-entity GET/POST covers MCP servers and npm packages; this surface is page-only for now.)
- State (latest)
- alive — the repository's last public activity was within 180 days of the observation
- Last public activity
- 2026-06-22
- Dated observations
- 2, from 2026-08-02 to 2026-08-31
- State changes
- 0 across the series
- Adoption (latest read 2026-08-02)
- 8 stars · 1 forks
- Method
- GitHub repository metadata + star/fork counts (authoritative)
- Source / evidence
- github.com/iamazeem/substitute-action
- Observed as of
- 2026-08-31
- Registry
- GitHub Actions
Interval-censoring. Observation window from 2026-08-02 to 2026-08-31, with 2 dated observations. A state transition inside an unobserved span is dated to that interval, not to a single day. The star and fork counts are the values read at the latest successful adoption observation (2026-08-02). Absence of an observation on a date is recorded as not observed, never as a state.
A dated observation series, not advice. Data under CC-BY-4.0. Check every dependency in one place: check your whole organization.
Dated observation series
| observation date | state | last public activity |
|---|---|---|
| 2026-08-02 | alive | 2026-06-22 |
| 2026-08-31 | alive | 2026-06-22 |
State-mutation history
Across 2 dated observations from 2026-08-02 to 2026-08-31, the recorded state did not change: it remained alive throughout the observed window.
When was it last active?
The last public activity read for this repository was dated 2026-06-22. State alive reflects the repository's last public activity was within 180 days of the observation.
What is its recorded state?
State alive is derived from the public GitHub repository metadata read on each observation date: the repository's last public activity was within 180 days of the observation.
What does that mean for projects using it?
At the latest adoption read (2026-08-02) the repository showed 8 stars and 1 forks — the adoption signal that qualifies this Action for a page. A workflow that pins this Action by a tag or SHA continues to resolve to its last published ref; a floating major-version ref has no newer release to resolve to. This is a dated observation, not advice about any named party.
What is the observation record?
The record is the dated series above: 2 observations from 2026-08-02 to 2026-08-31, each with a state and a last-activity date, plus 0 state change(s). A dispute re-reads the public GitHub metadata and issues a dated correction on this page.