@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 100 of 150)
| Version | Deps | Published |
|---|---|---|
| 0.6.81 | 16 / 0 | |
| 0.6.80 | 16 / 0 | |
| 0.6.79 | 16 / 0 | |
| 0.6.77 | 16 / 0 | |
| 0.6.75 | 16 / 0 | |
| 0.6.69 | 16 / 0 | |
| 0.6.68 | 16 / 0 | |
| 0.6.67 | 16 / 0 | |
| 0.6.66 | 16 / 0 | |
| 0.6.65 | 16 / 0 | |
| 0.6.64 | 16 / 0 | |
| 0.6.63 | 16 / 0 | |
| 0.6.62 | 16 / 0 | |
| 0.6.61 | 16 / 0 | |
| 0.6.60 | 16 / 0 | |
| 0.6.59 | 16 / 0 | |
| 0.6.58 | 16 / 0 | |
| 0.6.57 | 16 / 0 | |
| 0.6.56 | 16 / 0 | |
| 0.6.55 | 16 / 0 | |
| 0.6.53 | 16 / 0 | |
| 0.6.52 | 16 / 0 | |
| 0.6.50 | 16 / 0 | |
| 0.6.49 | 16 / 0 | |
| 0.6.48 | 16 / 0 | |
| 0.6.47 | 16 / 0 | |
| 0.6.46 | 16 / 0 | |
| 0.6.45 | 16 / 0 | |
| 0.6.44 | 16 / 0 | |
| 0.6.43 | 16 / 0 | |
| 0.6.42 | 16 / 0 | |
| 0.6.40 | 16 / 0 | |
| 0.6.39 | 16 / 0 | |
| 0.6.37 | 16 / 0 | |
| 0.6.36 | 16 / 0 | |
| 0.6.35 | 16 / 0 | |
| 0.6.34 | 16 / 0 | |
| 0.6.33 | 16 / 0 | |
| 0.6.32 | 16 / 0 | |
| 0.6.30 | 16 / 0 | |
| 0.6.29 | 16 / 0 | |
| 0.6.28 | 16 / 0 | |
| 0.6.27 | 16 / 0 | |
| 0.6.26 | 16 / 0 | |
| 0.6.22 | 16 / 0 | |
| 0.6.21 | 16 / 0 | |
| 0.6.20 | 16 / 0 | |
| 0.6.19 | 16 / 0 | |
| 0.6.18 | 16 / 0 | |
| 0.6.17 | 16 / 0 | |
| 0.6.16 | 16 / 0 | |
| 0.6.15 | 16 / 0 | |
| 0.6.14 | 16 / 0 | |
| 0.6.13 | 16 / 0 | |
| 0.6.12 | 16 / 0 | |
| 0.6.11 | 16 / 0 | |
| 0.6.10 | 16 / 0 | |
| 0.6.9 | 16 / 0 | |
| 0.6.8 | 16 / 0 | |
| 0.6.7 | 16 / 0 | |
| 0.6.6 | 16 / 0 | |
| 0.6.4 | 16 / 0 | |
| 0.6.3 | 16 / 0 | |
| 0.6.2 | 16 / 0 | |
| 0.6.1 | 16 / 0 | |
| 0.6.0 | 16 / 0 | |
| 0.5.7 | 16 / 0 | |
| 0.5.6 | 16 / 0 | |
| 0.5.5 | 16 / 0 | |
| 0.5.4 | 16 / 0 | |
| 0.5.3 | 16 / 0 | |
| 0.5.2 | 16 / 0 | |
| 0.5.1 | 16 / 0 | |
| 0.4.67 | 16 / 0 | |
| 0.4.66 | 16 / 0 | |
| 0.4.65 | 16 / 0 | |
| 0.4.64 | 16 / 0 | |
| 0.4.63 | 16 / 0 | |
| 0.4.62 | 16 / 0 | |
| 0.4.61 | 16 / 0 | |
| 0.4.60 | 16 / 0 | |
| 0.4.59 | 16 / 0 | |
| 0.4.57 | 16 / 0 | |
| 0.4.56 | 16 / 0 | |
| 0.4.55 | 16 / 0 | |
| 0.4.54 | 16 / 0 | |
| 0.4.52 | 16 / 0 | |
| 0.4.50 | 16 / 0 | |
| 0.4.49 | 16 / 0 | |
| 0.4.48 | 16 / 0 | |
| 0.4.47 | 16 / 0 | |
| 0.4.46 | 16 / 0 | |
| 0.4.45 | 16 / 0 | |
| 0.4.44 | 16 / 0 | |
| 0.4.43 | 16 / 0 | |
| 0.4.42 | 16 / 0 | |
| 0.4.41 | 16 / 0 | |
| 0.4.39 | 16 / 0 | |
| 0.4.38 | 16 / 0 | |
| 0.4.37 | 16 / 0 |
v0.6.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
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.5.3
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.54
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.52
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.49
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.46
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.45
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.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.