Is @lockness/auth-provider safe to use?

@lockness/auth-provider has no known vulnerabilities on the latest version (0.1.30). DepScope rates its health at 48/100 (high risk).

What is the latest version of @lockness/auth-provider?

The latest version of @lockness/auth-provider is 0.1.30, released 2026-01-17.

No known vulnerabilities on the latest version of @lockness/auth-provider.

No, @lockness/auth-provider is actively maintained. Latest release: 0.1.30 (2026-01-17).

DepScope has no curated alternatives for @lockness/auth-provider at this time.

License information for @lockness/auth-provider is not declared in the registry metadata.

jsrv0.1.30

Agnostic user providers for @lockness/auth. Support for Drizzle, Kysely, and more.

7 versions1 maintainers0 deps

/ 100

Health

safe to use

@lockness/[email protected] is safe to use (health: 48/100)

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/jsr/@lockness/auth-provider

First published · 2026-01-16T18:09:16.602736Z

Last updated · 2026-01-17T02:05:10.520232Z