Skip to content

Lastseen

Records dated maintenance states of software components, MCP servers and packages from public repository reads, with hash-chained observations.
At a glanceswept Oct 24, 2026

not read yet

Use

For
Developers and teams checking whether the software dependencies they rely on are still maintained
Runs as
API
Used for
  • check whether a repo's or package.json's dependencies are still maintained
  • look up a component's maintenance state as of a past date
  • verify published observation history against its public hash chain
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 26, 2026

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Lastseen with

Pick up to two.

All 10 alternatives to Lastseen →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Lastseen for?

Sign in to leave a note
Questions this page answers
  • What is Lastseen?

    Records dated maintenance states of software components, MCP servers and packages from public repository reads, with hash-chained observations. It is listed in the Atlas under Developer tools.

  • Who is Lastseen for?

    Developers and teams checking whether the software dependencies they rely on are still maintained

  • Do people use Lastseen?

    Little sign of use.

  • What are alternatives to Lastseen?

    In Developer tools, by use: World Monitor, Qodo, Vioscale AI, GreenCalculus, Programmes, LinkList.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk