Support
Email hello@libyears.com. A person reads it, usually the person who wrote the code you are asking about.
What to expect
Libyears is new and small. There is no ticketing system, no tiered support, and no published response time, because one we have not measured would be a number we invented. In practice: within a day, most days.
If something is broken and you are blocked, say so in the subject line. That is enough to jump the queue; there is no separate paid channel for it.
Before you write
Two answers cover most of what people ask.
A repository stopped updating. The dashboard says why, on the row itself, in words rather than a status code. The usual causes are that the app was removed from that repository’s selection, or the repository sits above your plan’s limit and scanning has paused. Nothing is deleted in either case.
A version looks wrong. A release published in the last fourteen days does not count as lag yet, so “latest” can differ from what npm outdated reports. The genuinely newest version is shown alongside it.
Bugs in the open-source parts
The lockfile parsers, the freshness metrics, the registry client and the CLI are MIT and developed in the open. A wrong number almost always originates in one of them, and a public issue with the lockfile that produced it is the fastest possible fix.
Security
Report a vulnerability to security@libyears.com. We will acknowledge within one working day and tell you what we found, whether or not it turns out to be exploitable. We will not threaten you for looking.
What the product can read, and what it does with it, is documented on the security page.
Getting your data out, or leaving
Every repository exports as CSV or CycloneDX from its own page. An owner can delete an entire organisation from settings without contacting us or sitting through a retention offer. Cancelling a subscription is one click in the same place.
If you leave, we would genuinely like to know why, but nothing is gated behind telling us.