Is @tamagui/babel-plugin-fully-specified safe to use?

@tamagui/babel-plugin-fully-specified has no known vulnerabilities on the latest version (2.0.0-rc.41). DepScope rates its health at 77/100 (moderate risk).

What is the latest version of @tamagui/babel-plugin-fully-specified?

The latest version of @tamagui/babel-plugin-fully-specified is 2.0.0-rc.41, released 2026-04-15.

Does @tamagui/babel-plugin-fully-specified have known vulnerabilities?

No known vulnerabilities on the latest version of @tamagui/babel-plugin-fully-specified.

Is @tamagui/babel-plugin-fully-specified deprecated?

No, @tamagui/babel-plugin-fully-specified is actively maintained. Latest release: 2.0.0-rc.41 (2026-04-15).

What are alternatives to @tamagui/babel-plugin-fully-specified?

Popular alternatives to @tamagui/babel-plugin-fully-specified in npm include: minimatch, wrap-ansi, @types/node, eslint-visitor-keys, ajv.

What license does @tamagui/babel-plugin-fully-specified use?

@tamagui/babel-plugin-fully-specified is licensed under MIT.

@tamagui/babel-plugin-fully-specified

npmv2.0.0-rc.41

not doing dist here for now since it is used by tamagui-build itself

License MITpermissive686 versions1 maintainers1 deps47,417 weekly dl

/ 100

Health

safe to use

@tamagui/[email protected] is safe to use (health: 77/100)

Health breakdown0 – 100

25/25

maintenance

10/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@babel/core

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@tamagui/babel-plugin-fully-specified