npmpackage.info

Gathering detailed insights and metrics for @types/toidentifier

@types/toidentifier

The repository for high quality TypeScript type definitions.

1.0.2

48,747

NOASSERTION

TypeScript

5,804,180 7

Installations

npm install @types/toidentifier

Score

98.6

Supply Chain

70.2

Quality

75.2

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

158

Total

60,189

Closed

9,511

Merged

50,520

Issues

Open

552

Total

8,052

Closed

7,500

Releases

0.1.450

Published on 04 Sept 2019

View all 1 releases

Developer

DefinitelyTyped

Developer Guide

BETA

Module System

Unable to determine the module system for this package.

Min. Node Version

Typescript Support

Yes

Node Version

NPM Version

Statistics

48,747 Stars

88,226 Commits

30,194 Forks

641 Watching

10 Branches

9,975 Contributors

Updated on 29 Nov 2024

Languages

TypeScript (99.9%)

JavaScript (0.09%)

Shell (0.01%)

Total Downloads

Cumulative downloads

Total Downloads

5,804,180

Last day

-3.2%

5,177

Compared to previous day

Last week

0.5%

32,971

Compared to previous week

Last month

6.5%

137,950

Compared to previous month

Last year

-40.8%

2,009,431

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Versions

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

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

10

Security-Policy

Determines if the project has published a security policy.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Binary-Artifacts

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

9

Code-Review

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

9

License

Determines if the project has defined a license.

8

Pinned-Dependencies

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

0

CII-Best-Practices

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

0

Token-Permissions

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

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

Score

7

/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