detect-conflicts 0.1.1

Check for conflicts, and get prompted for action (when needed), before writing a file to disk.

detect-conflicts@0.1.1 was published on 2015-08-19. Its manifest declares 13 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.

Deprecated: Package has been renamed to conflicts, please use that instead.

All detect-conflicts versions · Permanent reference to 0.1.1 · Latest release

Package specifications

Version0.1.1
License declarationMIT
Published2015-08-19T20:45:39.213Z
Node.js requirement>=0.10.0
Type declarationsNot declared
Runtime dependency count13
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies34
Repository stars2
Repository forks0

Install detect-conflicts 0.1.1

npm install detect-conflicts@0.1.1
pnpm add detect-conflicts@0.1.1
yarn add detect-conflicts@0.1.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Binary-Artifacts10/10 — no binaries found in the repo
Code-Review0/10 — Found 0/7 approved changesets -- score normalized to 0
SAST0/10 — no SAST tool detected
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy0/10 — security policy file not detected

Evidence and freshness