npmpackage.info

Gathering detailed insights and metrics for detect-conflict

detect-conflict

Small utility library that check if a new file content can be merged safely in the on-disk existing file.

1.0.1

MIT

JavaScript

71,921,196 3

Installations

npm install detect-conflict

Pull Requests

Open

1

Total

4

Closed

1

Merged

2

Issues

Open

0

Total

3

Closed

3

Releases

v1.0.1

Published on 04 Jul 2016

View all 1 releases

Developer

SBoudrias

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

6.2.2

NPM Version

3.9.5 Statistics

11 Stars

8 Commits

1 Forks

2 Watching

30 Branches

1 Contributors

Updated on 09 Dec 2021

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

71,921,196

Last day

-20.6%

25,740

Compared to previous day

Last week

-13.4%

180,594

Compared to previous week

Last month

224.4%

856,938

Compared to previous month

Last year

-12.4%

4,238,440

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

mocha

Versions

detect-conflict

Small utility library that check if a new file content can be merged safely in the on-disk existing file.

Usage

Example

1var conflict = require('detect-conflict');
2
3var isConflicting = conflict('some-file-name.js', 'var newContent;');

It'll return true if a conflict is found, false otherwise.

API

`conflict(filepath : string, contents : Buffer | String)`

If the contents is passed as a string, we assume it is utf8 encoded. Pass a Buffer if you want to compare special encoding.

If filepath points to a directory, we'll always return true.

No vulnerabilities found.

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.

10

License

Determines if the project has defined a license.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

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

0

CII-Best-Practices

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

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

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

/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