Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate confident and imprecise detectors, introduce detector identification #717

Merged
merged 4 commits into from
Jan 7, 2025

Conversation

Borewit
Copy link
Collaborator

@Borewit Borewit commented Jan 2, 2025

Extend the Detector type with an id property, which allows users to understand which detector is doing what. The core detectors are seperated in:

  • default.safe: Safe core detectors
  • default.unsafe: Collection of detectors with higher probability of false positive

Resolves: #483

@Borewit Borewit self-assigned this Jan 2, 2025
Extend the `Detector` type with an `id` property, which allows users to understand which detector is doing what.
The core detectors are seperated in:
Extend the `Detector` type with an `id` property, which allows users to understand which detector is doing what. The core detectors are seperated in:
- `default.safe`: Safe core detectors
- `default.unsafe`: Collection of detectors with higher probability of false positive
@Borewit Borewit marked this pull request as ready for review January 2, 2025 17:01
@sindresorhus
Copy link
Owner

sindresorhus commented Jan 2, 2025

Is "unsafe" the right word? It makes it sound like they have vulnerabilities, which is not correct.

Maybe: unreliable, unstable, imprecise, fragile

@Borewit
Copy link
Collaborator Author

Borewit commented Jan 2, 2025

Loose, lax, speculative, unreliable, weak, sparse, indistinct?

@sindresorhus
Copy link
Owner

Lets go with fragile.

core.js Outdated Show resolved Hide resolved
- Confident (`core`): Represents detections with a high degree of certainty in identifying the correct file type.
- Imprecise (`core.imprecise`): Represents detections with limited supporting data, resulting in a higher likelihood of false positives.
@sindresorhus sindresorhus changed the title Separate safe from unsafe detectors, introduce detector identification Separate confident and imprecise detectors, introduce detector identification Jan 7, 2025
@sindresorhus sindresorhus merged commit 356bce8 into main Jan 7, 2025
6 checks passed
@sindresorhus sindresorhus deleted the add-detector-id branch January 7, 2025 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow disabling unsafe types?
3 participants