Upstream software project

editorconfig-checker

Tool to verify that your files are in harmony with your .editorconfig

About editorconfig-checker

Tool to verify that your files are in harmony with your .editorconfig

This project links 1 native package record across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

editorconfig-checker repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.editorconfig-checker: recorded package coverageopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
editorconfig-checker
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
opensuse-tumbleweed
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This is a tool to check if your files consider your .editorconfig rules. Most tools—like linters, for example—only test one filetype and need an extra configuration. This tool only needs your .editorconfig to check all files. If you don't know about editorconfig already you can read about it here: editorconfig.org.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Tumbleweed

  1. Package editorconfig-checker

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Tool to verify that your files are in harmony with your .editorconfig

    3.11.2-1.1: x86_64

    Source: editorconfig-checker

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.