Is should-send-same-site-none safe to use?

should-send-same-site-none has no known vulnerabilities on the latest version (2.0.5). DepScope rates its health at 49/100 (high risk).

What is the latest version of should-send-same-site-none?

The latest version of should-send-same-site-none is 2.0.5, released 2020-04-29.

Does should-send-same-site-none have known vulnerabilities?

No known vulnerabilities on the latest version of should-send-same-site-none.

Is should-send-same-site-none deprecated?

No, should-send-same-site-none is actively maintained. Latest release: 2.0.5 (2020-04-29).

What are alternatives to should-send-same-site-none?

Popular alternatives to should-send-same-site-none in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does should-send-same-site-none use?

should-send-same-site-none is licensed under MIT.

should-send-same-site-none

npmv2.0.5

A simple utility to detect incompatible user agents for `SameSite=None` cookie attribute

License MITpermissive9 versions1 maintainers0 deps47,795 weekly dl

linsight/should-send-same-site-none

/ 100

Health

use with caution

[email protected] low health (49/100) — consider alternatives

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.5 KBminified

0.7 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/should-send-same-site-none