npmpackage.info

Gathering detailed insights and metrics for eslint-plugin-no-type-assertion

eslint-plugin-no-type-assertion

Disallow type assertions in TypeScript code

1.3.0

MIT

JavaScript

1,469,884 2.5

Installations

npm install eslint-plugin-no-type-assertion

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

3

Total

6

Closed

3

Releases

Unable to fetch releases

Developer

Dremora

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=12.0.0

Typescript Support

No

Node Version

14.18.1

NPM Version

6.14.15 Statistics

29 Stars

17 Commits

1 Forks

3 Watching

1 Branches

1 Contributors

Updated on 13 Oct 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

1,469,884

Last day

29.7%

7,434

Compared to previous day

Last week

45.8%

38,810

Compared to previous week

Last month

4.7%

128,772

Compared to previous month

Last year

178.8%

1,028,134

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Peer Dependencies

eslint

Dev Dependencies

@typescript-eslint/parser eslint jest prettier typescript

Versions

eslint-plugin-no-type-assertion

Disallow type assertions in TypeScript code. The rule will forbid both as operator and the angle-bracketed syntax, unless used for const assertions or with the unknown type. The rule also forbids non-null assertions.

The following code becomes invalid:

1const foo: unknown = 42;
2
3const notAString = <string>foo; // can't perform angle-bracketed type assertion
4const alsoNotAString = foo as string; // can't use `as` operator for type assertion
5
6const objectWithOptionalProperty: { a?: number } = {};
7
8const notANumber = objectWithOptionalProperty.a! / 2; // can't use non-null assertion operator

Installation

Ensure you have ESLint and @typescript-eslint/parser installed:

$ yarn add eslint @typescript-eslint/parser -D

Next, install this plugin:

$ yarn add eslint-plugin-no-type-assertion -D

Configuration

In your ESLint configuration, ensure you're using @typescript-eslint/parser as a parser and it's set up correctly:

1{
2  "parser": "@typescript-eslint/parser",
3  "parserOptions": {
4    "ecmaVersion": 2018
5  }
6}

Add eslint-plugin-no-type-assertion to the plugin list:

1{
2  "plugins": ["no-type-assertion"]
3}

Enable the rule:

1{
2  "rules": {
3    "no-type-assertion/no-type-assertion": "error"
4  }
5}

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

SAST

Determines if the project uses static code analysis.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.5

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More