Installations

npm install @types/parse-filepath

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Score

99

Supply Chain

93.5

Quality

75.2

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

173

Total

60,510

Closed

9,552

Merged

50,785

Issues

Open

560

Total

8,064

Closed

7,504

Releases

1

0.1.450

Published on 04 Sept 2019

View all 1 releases

Contributors

9,977

View all 9,977 contributors

Languages

3

TypeScript

JavaScript

Shell

TypeScript (99.9%)

JavaScript (0.09%)

Shell (0.01%)

Developer

DefinitelyTyped

Download Statistics

Total Downloads

5,268,265

Last Day

6,765

Last Week

31,372

Last Month

139,618

Last Year

965,237

GitHub Statistics

49,039 Stars

88,511 Commits

30,274 Forks

641 Watching

5 Branches

9,977 Contributors

Maintainers

1

Package Meta Information

Latest Version

1.0.2

Package Id

@types/parse-filepath@1.0.2

Unpacked Size

5.33 kB

Size

1.85 kB

File Count

5

Publised On

07 Nov 2023

Total Downloads

Cumulative downloads

Total Downloads

5,268,265

Last day

15.9%

6,765

Compared to previous day

Last week

-10.3%

31,372

Compared to previous week

Last month

15.2%

139,618

Compared to previous month

Last year

52.1%

965,237

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Versions

Installation

npm install --save @types/parse-filepath

Summary

This package contains type definitions for parse-filepath (https://github.com/jonschlinkert/parse-filepath).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/parse-filepath.

index.d.ts

1export = parseFilepath;
2
3/**
4 * Pollyfill for node.js `path.parse()`, parses a filepath into an object.
5 *
6 * @param filepath
7 */
8declare function parseFilepath(filepath: string): parseFilepath.ParsedPath;
9
10declare namespace parseFilepath {
11    interface ParsedPath {
12        /**
13         * The root of the path such as `'/'` or `'c:\'`
14         */
15        root: string;
16        /**
17         * The full directory path such as `'/home/user/dir'` or `'c:\path\dir'`
18         */
19        dir: string;
20        /**
21         * The file name including extension (if any) such as `'index.html'`
22         */
23        base: string;
24        /**
25         * The file extension (if any) such as `'.html'`
26         */
27        ext: string;
28        /**
29         * The file name without extension (if any) such as `'index'`
30         */
31        name: string;
32
33        /**
34         * alias for `ext`
35         */
36        extname: string;
37        /**
38         * alias for `base`
39         */
40        basename: string;
41        /**
42         * alias for `dir`
43         */
44        dirname: string;
45        /**
46         * alias for `name`
47         */
48        stem: string;
49
50        /**
51         * the original filepath
52         */
53        path: string;
54
55        /**
56         * fully resolved, absolute filepath
57         */
58        absolute: string;
59        /**
60         * `true` if the given path is absolute
61         */
62        isAbsolute: boolean;
63    }
64}
65

Additional Details

Last updated: Tue, 07 Nov 2023 09:09:39 GMT
Dependencies: none

Credits

These definitions were written by BendingBender.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

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

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

License

Determines if the project has defined a license.

8

Code-Review

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

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

6.9

/10

Last Scanned on 2025-01-13

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