Installations

npm install @stoplight/path

Score

99.5

Supply Chain

83.4

Quality

76.9

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

5

Total

49

Closed

23

Merged

21

Issues

Open

1

Total

3

Closed

2

Releases

14

v2.0.1

Published on 19 Mar 2024

v2.0.0

Published on 01 Feb 2023

v2.0.0-beta.2

Published on 01 Feb 2023

v2.0.0-beta.1

Published on 01 Feb 2023

v1.3.2

Published on 29 Jul 2020

v1.3.1

Published on 06 Feb 2020

View all 14 releases

Developer

stoplightio

Developer Guide

BETA

Module System

CommonJS, ESM

Min. Node Version

^12.20 || >=14.13

Typescript Support

Yes

Node Version

20.11.1

NPM Version

8.19.3 Statistics

2 Stars

31 Commits

1 Forks

17 Watching

9 Branches

59 Contributors

Updated on 01 Feb 2023

Bundle Size

9.63 kB

Minified

3.43 kB

Minified + Gzipped

Bundlephobia

Languages

TypeScript (92.16%)

PEG.js (5.96%)

JavaScript (1.89%)

Total Downloads

Cumulative downloads

Total Downloads

62,390,745

Last day

-30.7%

117,839

Compared to previous day

Last week

-7.8%

754,226

Compared to previous week

Last month

2.3%

3,290,182

Compared to previous month

Last year

66.6%

30,626,913

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

24

Versions

@stoplight/path

View the changelog: Releases

Features

Awesome: It is.
.. more features

Installation

Supported in modern browsers and node.

1# latest stable
2yarn add @stoplight/path

Usage

1import * as path from '@stoplight/path';
2
3// ...example

Contributing

Clone repo.
Create / checkout feature/{name}, chore/{name}, or fix/{name} branch.
Install deps: yarn.
Make your changes.
Run tests: yarn test.prod.
Stage relevant files to git.
Commit: yarn commit. NOTE: Commits that don't follow the conventional format will be rejected. yarn commit creates this format for you, or you can put it together manually and then do a regular git commit.
Push: git push.
Open PR targeting the master branch.

No vulnerabilities found.

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.

9

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

CII-Best-Practices

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

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3.4

/10

Last Scanned on 2024-11-18

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