@trackunit/eslint-plugin-trackunit
A shared ESLint plugin and configuration preset for Trackunit projects. It bundles Trackunit-specific custom rules alongside curated third-party plugin configurations into ready-to-use flat-config presets for ESLint 9+.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:toplevel-fetch | AI (semgrep): fetch() call is inside an ESLint rule's example/test fixture file, not production code — stable false positive for this package. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.txt | AI (license): Custom license file reference is legitimate for proprietary packages. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice recommendation, not a security blocker for this package. | ai | |
| dependencies | unvetted-dep:@nx/eslint-plugin | AI (dependencies): Well-known Nx monorepo tooling; stable dependency for this ESLint plugin package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-no-null | AI (dependencies): Established ESLint plugin; no malicious indicators, appropriate for this package's purpose. | ai |
Versions (showing 50 of 150)
| Version | Deps | Published |
|---|---|---|
| 0.4.35 | 16 / 0 | |
| 0.4.34 | 16 / 0 | |
| 0.4.33 | 16 / 0 | |
| 0.4.32 | 16 / 0 | |
| 0.4.31 | 16 / 0 | |
| 0.4.30 | 16 / 0 | |
| 0.4.29 | 16 / 0 | |
| 0.4.28 | 16 / 0 | |
| 0.4.27 | 16 / 0 | |
| 0.4.25 | 16 / 0 | |
| 0.4.24 | 16 / 0 | |
| 0.4.23 | 16 / 0 | |
| 0.4.22 | 16 / 0 | |
| 0.4.21 | 16 / 0 | |
| 0.4.20 | 16 / 0 | |
| 0.4.19 | 18 / 0 | |
| 0.4.18 | 18 / 0 | |
| 0.4.17 | 18 / 0 | |
| 0.4.16 | 18 / 0 | |
| 0.4.15 | 18 / 0 | |
| 0.4.14 | 18 / 0 | |
| 0.4.13 | 18 / 0 | |
| 0.4.12 | 18 / 0 | |
| 0.4.11 | 18 / 0 | |
| 0.4.10 | 18 / 0 | |
| 0.4.9 | 18 / 0 | |
| 0.4.8 | 18 / 0 | |
| 0.4.7 | 18 / 0 | |
| 0.4.6 | 18 / 0 | |
| 0.4.1 | 18 / 0 | |
| 0.4.0 | 18 / 0 | |
| 0.3.23 | 18 / 0 | |
| 0.3.22 | 18 / 0 | |
| 0.3.21 | 18 / 0 | |
| 0.3.20 | 18 / 0 | |
| 0.3.18 | 18 / 0 | |
| 0.3.17 | 18 / 0 | |
| 0.3.16 | 18 / 0 | |
| 0.3.15 | 18 / 0 | |
| 0.3.14 | 18 / 0 | |
| 0.3.13 | 18 / 0 | |
| 0.3.12 | 18 / 0 | |
| 0.3.11 | 18 / 0 | |
| 0.3.10 | 18 / 0 | |
| 0.3.9 | 18 / 0 | |
| 0.3.2 | 17 / 0 | |
| 0.2.0 | 17 / 0 | |
| 0.1.0 | 17 / 0 | |
| 0.0.4 | 17 / 0 | |
| 0.0.2 | 17 / 0 |
v0.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.