Is @inlay/render safe to use?

@inlay/render has no known vulnerabilities on the latest version (0.3.1). DepScope rates its health at 56/100 (high risk).

What is the latest version of @inlay/render?

The latest version of @inlay/render is 0.3.1, released 2026-03-30.

Does @inlay/render have known vulnerabilities?

No known vulnerabilities on the latest version of @inlay/render.

Is @inlay/render deprecated?

No, @inlay/render is actively maintained. Latest release: 0.3.1 (2026-03-30).

What are alternatives to @inlay/render?

Popular alternatives to @inlay/render in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @inlay/render use?

License information for @inlay/render is not declared in the registry metadata.

@inlay/render

npmv0.3.1

Server-side component resolution for Inlay element trees. Given an element like `<com.example.Greeting name="world">`, the renderer looks up the component implementation, expands it, and recurses until everything is primitives the host can render.

16 versions1 maintainers2 deps24 weekly dl

/ 100

Health

use with caution

@inlay/[email protected] low health (56/100) — consider alternatives

Moderate health score (56/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

@atproto/lexicon @atproto/syntax

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@inlay/render