What did Hlido score @cleocode/lafs?

@cleocode/lafs scored 57/100 (STEADY) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

@cleocode/lafs

Name: @cleocode/lafs review
Item: @cleocode/lafs
Rating: 57
Author: Hlido Editor

Coding · tested 2026-05-23 · re-test due 2026-08-21 · by the Hlido desk, not the vendor

In short: Functional coding library with decent utility, but lacks comprehensive documentation and community support.

0 PASS · 5 FAIL of 5 public-surface claims

Visit @cleocode/lafs → scorecard.json

Quick answer

@cleocode/lafs scores 57/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-05-23). STEADY (57) due to its functional capabilities, but it lacks the robust documentation and community support that would elevate it to a higher tier. Pricing was not findable on the public surface when tested.

Hlido Editor · 2026-05-23

The @cleocode/lafs library serves its purpose within the coding ecosystem, providing a set of functionalities that can be useful for developers. However, it suffers from a lack of thorough documentation and community engagement, which can hinder its adoption and effective use. While it functions adequately for basic tasks, users may find themselves struggling to implement more complex features due to insufficient guidance. Compared to more established libraries, it falls short in terms of user support and resources. For those who are comfortable navigating less-documented tools, it may still offer value, but many users might prefer alternatives that come with stronger community backing and clearer instructions.

Why STEADY

STEADY (57) due to its functional capabilities, but it lacks the robust documentation and community support that would elevate it to a higher tier. Improved documentation or a growing user community could shift this tier upward.

Public-surface checklist

FAIL Homepage loads (required)
FAIL Primary value prop (required)
FAIL Cta present (required)
FAIL Pricing or access
FAIL Evidence or demo

What it does well

Provides basic functionalities for coding tasks
Can be integrated into existing projects with relative ease
Offers a straightforward API for developers familiar with similar libraries

What it fails at

Documentation is sparse, making it hard for new users to get started
Limited community support and resources for troubleshooting
Lacks advanced features found in more popular libraries

Red flags

Sparse documentation may lead to implementation challenges
Limited community engagement could indicate potential stagnation

Best for

Developers comfortable with trial and error in less-documented environments
Small projects where basic functionalities suffice
Users looking for lightweight coding solutions without extensive overhead

Not recommended for

Beginners needing comprehensive guidance and support
Projects requiring advanced features or robust community resources
Teams that prioritize well-documented tools for collaboration

Pricing & access

Pricing findable on the public surfaceFAIL (tested 2026-05-23)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-05-23.

Compared to

Lodash documentation-and-support
Lodash is a well-documented and widely supported utility library with a strong community. Choose Lodash for comprehensive features and community resources, while @cleocode/lafs may suffice for simpler needs.
Underscore community-engagement
Underscore provides similar functionalities with better documentation and community backing. Opt for Underscore if you need more reliable support and resources.

Agent relevance

No programmatic surfaces

Agentic-Commerce Readiness 9/100 · CLOSED

Independent readiness for agent delegation & transaction. How it’s scored · check live

None — the library operates as a coding utility without direct integration paths for agents.

Agent-friendly score: 3/10

scorecard.json · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-08-21

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/cleocode-lafs.svg)](https://hlido.eu/check/?agent=cleocode-lafs)

HTML

<a href="https://hlido.eu/check/?agent=cleocode-lafs"><img src="https://hlido.eu/badge/cleocode-lafs.svg" alt="Hlido trust score"></a>