eslint-plugin-compat
Lint browser compatibility of API used
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; stable for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): jtran was a contributor; removal alongside CI publish migration is benign. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): globals is a well-known ESLint ecosystem package; its addition is appropriate for a browser-compat linting plugin. No malicious signal. | ai | |
| phantom-deps | phantom-dep:@mdn/browser-compat-data | AI (phantom-deps): @mdn/browser-compat-data is a core data dependency of this plugin; indirect import pattern is expected for a data package used via config/data files. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 7 / 32 | |
| 7.0.1 | 7 / 32 | |
| 7.0.0 | 7 / 32 | |
| 6.2.1 | 7 / 32 | |
| 6.2.0 | 8 / 32 | |
| 6.1.0 | 8 / 32 | |
| 6.0.2 | 8 / 29 | |
| 6.0.1 | 8 / 29 | |
| 6.0.0 | 8 / 29 | |
| 5.0.0 | 8 / 32 | |
| 4.2.0 | 7 / 30 | |
| 4.1.4 | 8 / 28 | |
| 4.1.3 | 7 / 29 | |
| 4.1.2 | 7 / 29 | |
| 4.1.1 | 8 / 31 | |
| 4.1.0 | 9 / 30 | |
| 4.0.2 | 8 / 31 | |
| 4.0.1 | 8 / 31 | |
| 4.0.0 | 8 / 31 | |
| 3.13.0 | 8 / 30 | |
| 3.12.0 | 8 / 30 | |
| 3.11.1 | 8 / 30 | |
| 3.11.0 | 8 / 30 | |
| 3.10.0 | 8 / 30 | |
| 3.9.0 | 8 / 29 | |
| 3.8.0 | 8 / 26 | |
| 3.7.0 | 7 / 11 | |
| 3.6.0 | 7 / 11 | |
| 3.5.1 | 7 / 17 | |
| 3.3.0 | 7 / 16 | |
| 3.2.0 | 6 / 16 | |
| 3.1.2 | 6 / 16 | |
| 3.1.1 | 6 / 16 | |
| 3.1.0 | 6 / 16 | |
| 3.0.1 | 6 / 17 | |
| 3.0.0 | 6 / 17 | |
| 2.7.0 | 4 / 17 | |
| 2.6.3 | 4 / 17 | |
| 2.6.2 | 4 / 16 | |
| 2.6.1 | 4 / 16 | |
| 2.6.0 | 4 / 16 | |
| 2.5.1 | 5 / 19 | |
| 2.5.0 | 5 / 19 | |
| 2.4.0 | 5 / 19 | |
| 2.3.0 | 5 / 18 | |
| 2.2.0 | 5 / 18 | |
| 2.1.0 | 4 / 18 | |
| 2.0.1 | 4 / 18 | |
| 2.0.0 | 4 / 17 | |
| 1.0.4 | 4 / 25 | |
| 1.0.3 | 4 / 25 | |
| 1.0.2 | 4 / 25 | |
| 1.0.1 | 3 / 24 | |
| 1.0.0 | 3 / 26 | |
| 0.1.3 | 2 / 26 | |
| 0.1.2 | 2 / 26 | |
| 0.1.1 | 2 / 26 | |
| 0.1.0 | 2 / 26 | |
| 0.0.7 | 2 / 27 | |
| 0.0.6 | 2 / 27 | |
| 0.0.5 | 1 / 28 | |
| 0.0.4 | 1 / 28 | |
| 0.0.1 | 0 / 0 |
v7.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.