eslint-plugin-import-x
Import with sanity.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:get-tsconfig | AI (dependencies): get-tsconfig is a legitimate, widely-used utility for resolving tsconfig files; its use is appropriate and expected for an ESLint import plugin with TypeScript support. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 3.4M weekly downloads and strong publisher track record; lack of Sigstore provenance is not a security risk for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in module-require.js is a standard ESLint plugin pattern for resolving modules within ESLint's own module context. Not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-node | AI (phantom-deps): eslint-import-resolver-node is a resolver referenced in config/docs but not directly imported in code — expected pattern for this plugin's resolver architecture. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from personal account to GitHub Actions CI/CD with SLSA provenance — this is a security improvement, not a risk. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature ESLint plugin with 67 versions; dormancy reflects stability. SLSA provenance confirms legitimate CI/CD publish. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 4.16.2 | 10 / 0 | |
| 4.16.1 | 9 / 0 | |
| 4.16.0 | 9 / 0 | |
| 4.15.2 | 9 / 0 | |
| 4.15.1 | 9 / 0 | |
| 4.15.0 | 9 / 0 | |
| 4.14.2 | 9 / 0 | |
| 4.14.1 | 9 / 0 | |
| 4.14.0 | 10 / 0 | |
| 4.13.3 | 11 / 0 | |
| 4.13.2 | 11 / 0 | |
| 4.13.1 | 11 / 0 | |
| 4.13.0 | 11 / 0 | |
| 4.12.2 | 11 / 0 | |
| 4.12.1 | 11 / 0 | |
| 4.12.0 | 11 / 0 | |
| 4.11.1 | 11 / 0 | |
| 4.11.0 | 11 / 0 | |
| 4.10.6 | 13 / 0 | |
| 4.10.5 | 13 / 0 | |
| 4.10.4 | 13 / 0 | |
| 4.10.3 | 13 / 0 | |
| 4.10.2 | 13 / 0 | |
| 4.10.1 | 13 / 0 | |
| 4.10.0 | 13 / 0 | |
| 4.9.4 | 12 / 0 | |
| 4.9.3 | 12 / 0 | |
| 4.9.2 | 12 / 0 | |
| 4.9.1 | 12 / 0 | |
| 4.9.0 | 11 / 0 | |
| 4.8.1 | 11 / 0 | |
| 4.8.0 | 11 / 0 | |
| 4.7.2 | 12 / 0 | |
| 4.7.1 | 12 / 0 | |
| 4.7.0 | 12 / 71 | |
| 4.6.1 | 13 / 62 | |
| 4.6.0 | 12 / 63 | |
| 4.5.1 | 12 / 63 | |
| 4.5.0 | 11 / 64 | |
| 4.4.3 | 10 / 64 | |
| 4.4.2 | 10 / 64 | |
| 4.4.0 | 10 / 64 | |
| 4.3.1 | 10 / 64 | |
| 4.3.0 | 10 / 64 | |
| 4.2.1 | 10 / 64 | |
| 4.2.0 | 10 / 64 | |
| 4.1.1 | 11 / 64 | |
| 4.1.0 | 11 / 61 | |
| 4.0.0 | 11 / 61 | |
| 3.1.0 | 10 / 55 | |
| 3.0.1 | 11 / 55 |
v4.16.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. 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.
v4.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.15.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.