@xylabs/eslint-config-flat
ESLint Config used throughout XY Labs TypeScript/JavaScript libraries and react projects
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-volume publisher with 450 versions; rapid publishes are consistent with automated CI release pipelines for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email on prior approved versions; not a new external actor. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removal paired with atrouw addition reflects an internal maintainer rotation, not a takeover. | ai | |
| provenance | no-provenance | AI (provenance): Dev tooling package from established org; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 55 of 156)
| Version | Deps | Published |
|---|---|---|
| 7.4.21 | 10 / 6 | |
| 7.4.20 | 10 / 6 | |
| 7.4.19 | 10 / 5 | |
| 7.4.18 | 10 / 5 | |
| 7.4.17 | 10 / 5 | |
| 7.4.16 | 10 / 5 | |
| 7.4.15 | 10 / 5 | |
| 7.4.14 | 10 / 5 | |
| 7.4.13 | 10 / 5 | |
| 7.4.12 | 10 / 5 | |
| 7.4.11 | 10 / 5 | |
| 7.4.10 | 10 / 5 | |
| 7.4.9 | 10 / 5 | |
| 7.4.8 | 10 / 5 | |
| 7.4.7 | 10 / 5 | |
| 7.4.6 | 10 / 5 | |
| 7.4.5 | 10 / 5 | |
| 7.4.4 | 10 / 5 | |
| 7.4.3 | 10 / 5 | |
| 7.4.2 | 10 / 5 | |
| 7.4.1 | 10 / 5 | |
| 7.4.0 | 10 / 5 | |
| 7.3.2 | 10 / 5 | |
| 7.3.1 | 10 / 5 | |
| 7.2.32 | 10 / 5 | |
| 7.2.30 | 10 / 5 | |
| 7.2.29 | 10 / 5 | |
| 7.2.28 | 10 / 5 | |
| 7.2.27 | 10 / 5 | |
| 7.2.26 | 10 / 5 | |
| 7.2.25 | 10 / 5 | |
| 7.2.15 | 10 / 5 | |
| 7.2.11 | 10 / 5 | |
| 7.2.10 | 10 / 5 | |
| 7.2.9 | 10 / 5 | |
| 7.2.8 | 10 / 5 | |
| 7.2.7 | 10 / 5 | |
| 7.2.6 | 10 / 5 | |
| 7.2.5 | 10 / 5 | |
| 7.2.4 | 10 / 5 | |
| 7.2.3 | 10 / 5 | |
| 7.2.2 | 10 / 5 | |
| 7.1.8 | 10 / 5 | |
| 7.1.7 | 10 / 5 | |
| 7.1.6 | 10 / 5 | |
| 7.1.5 | 10 / 5 | |
| 7.1.4 | 10 / 5 | |
| 7.1.3 | 10 / 5 | |
| 7.1.2 | 10 / 5 | |
| 7.1.1 | 10 / 5 | |
| 7.1.0 | 10 / 5 | |
| 7.0.3 | 10 / 5 | |
| 7.0.2 | 10 / 5 | |
| 7.0.1 | 10 / 5 | |
| 7.0.0 | 10 / 5 |
v7.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.