Gathering detailed insights and metrics for @bcoe/dotignore
Gathering detailed insights and metrics for @bcoe/dotignore
Installations
npm install @bcoe/dotignoreDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
8.8.1
NPM Version
5.4.2
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
bmeck
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
9 Stars
56 Commits
6 Forks
3 Watchers
3 Branches
3 Contributors
Updated on May 07, 2023
Maintainers
1
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
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Dev Dependencies
4
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.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
security policy file detected
Details
- Info: security policy file detected: .github/SECURITY.md:1
- Info: Found linked content: .github/SECURITY.md:1
- Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy
- Info: Found text in security policy: .github/SECURITY.md:1
Reason
Found 2/28 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/node-aught.yml:7: update your workflow using https://app.stepsecurity.io/secureworkflow/bmeck/dotignore/node-aught.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/node-pretest.yml:7: update your workflow using https://app.stepsecurity.io/secureworkflow/bmeck/dotignore/node-pretest.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/node-tens.yml:7: update your workflow using https://app.stepsecurity.io/secureworkflow/bmeck/dotignore/node-tens.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/rebase.yml:7: update your workflow using https://app.stepsecurity.io/secureworkflow/bmeck/dotignore/rebase.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/require-allow-edits.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/bmeck/dotignore/require-allow-edits.yml/master?enable=pin
- Info: 0 out of 5 third-party GitHubAction dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/node-aught.yml:1
- Warn: no topLevel permission defined: .github/workflows/node-pretest.yml:1
- Warn: no topLevel permission defined: .github/workflows/node-tens.yml:1
- Warn: no topLevel permission defined: .github/workflows/rebase.yml:1
- Warn: no topLevel permission defined: .github/workflows/require-allow-edits.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 4 are checked with a SAST tool
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