Is full-name-splitter safe to use?

full-name-splitter has no known vulnerabilities on the latest version (1.1.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of full-name-splitter?

The latest version of full-name-splitter is 1.1.1, released 2017-03-10.

Does full-name-splitter have known vulnerabilities?

No known vulnerabilities on the latest version of full-name-splitter.

Is full-name-splitter deprecated?

No, full-name-splitter is actively maintained. Latest release: 1.1.1 (2017-03-10).

What are alternatives to full-name-splitter?

Popular alternatives to full-name-splitter in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does full-name-splitter use?

full-name-splitter is licensed under MIT.

full-name-splitter

npmv1.1.1

Splits a string containing a (Western) person's full name into first and last name components

License MITpermissive2 versions1 maintainers0 deps5,686 weekly dl

/ 100

Health

safe to use

[email protected] is safe to use (health: 45/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/full-name-splitter