npmpackage.info

Gathering detailed insights and metrics for @bcoe/dotignore

@bcoe/dotignore - 0.1.2 | npmpackage.info

@bcoe/dotignore

ignorefile/includefile matching .gitignore spec

0.1.2

JavaScript

3.7

Installations

npm install @bcoe/dotignore

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

8.8.1

NPM Version

5.4.2 Pull Requests

Open

1

Total

6

Closed

1

Merged

4

Issues

Open

2

Total

4

Closed

2

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

bmeck

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

9 Stars

56 Commits

6 Forks

3 Watchers

3 Branches

3 Contributors

Updated on May 07, 2023

Maintainers

View All 3 Contributors

Package Meta Information

Latest Version

0.1.2

Package Id

@bcoe/dotignore@0.1.2

Size

2.70 kB

NPM Version

5.4.2

Node Version

8.8.1

Published on

Jan 02, 2018

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

minimatch

Dev Dependencies

covert jscs standard-version tape

dotignore

`ignored $IGNOREFILE`

Check the ignorefile against the current directory. Print out if a file should be ignored by prefixing with a -. If the file should not be ignored prefix it with a +.

API

exports.createMatcher(str)

Return a Matcher that fully matches the str argument.

str should conform to the .gitignore specification.

Matcher.shouldIgnore(name)

Test that all the rules provided to create the matcher match the name given. / is expected as the path delimiter. Returns true if the name should be ignored.

LICENSE

MIT

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

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

9

Security-Policy

Determines if the project has published a security policy.

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

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

Fuzzing

Determines if the project uses fuzzing.

0

License

Determines if the project has defined a license.

0

Branch-Protection

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

0

SAST

Determines if the project uses static code analysis.

Score

3.7

/10

Last Scanned on 2025-07-07

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