Is @financial-times/o-normalise safe to use?

@financial-times/o-normalise has no known vulnerabilities on the latest version (3.3.3). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of @financial-times/o-normalise?

The latest version of @financial-times/o-normalise is 3.3.3, released 2026-02-26.

Does @financial-times/o-normalise have known vulnerabilities?

No known vulnerabilities on the latest version of @financial-times/o-normalise.

Is @financial-times/o-normalise deprecated?

No, @financial-times/o-normalise is actively maintained. Latest release: 3.3.3 (2026-02-26).

What are alternatives to @financial-times/o-normalise?

Popular alternatives to @financial-times/o-normalise in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @financial-times/o-normalise use?

@financial-times/o-normalise is licensed under MIT.

@financial-times/o-normalise

npmv3.3.3

Provides base styles and resets for stylesheets. Includes standardised utilities, such as visually hiding components or adding a consistent focus state.

License MITpermissive34 versions11 maintainers0 deps

/ 100

Health

use with caution

@financial-times/[email protected] low health (62/100) — consider alternatives

Moderate health score (62/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

5/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/@financial-times/o-normalise