@eslint-sukka/react
Sukka's ESLint config
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://skk.moe | AI (email-domain): https://skk.moe is the author's homepage URL used in the author field, not an email address; domain is active and belongs to the known maintainer SukkaW. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-refresh | AI (phantom-deps): ESLint config package; plugins referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-compiler | AI (phantom-deps): ESLint config package; plugins referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@next/eslint-plugin-next | AI (phantom-deps): Framework-scoped ESLint plugin; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/types | AI (phantom-deps): TypeScript ESLint types referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/utils | AI (phantom-deps): TypeScript ESLint utils referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:foxts | AI (phantom-deps): ESLint config package; deps loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-ssr-friendly | AI (phantom-deps): ESLint plugin referenced in config files, not directly imported. | ai | |
| phantom-deps | phantom-dep:@eslint-sukka/eslint-plugin-stylistic | AI (phantom-deps): Same-org ESLint plugin; loaded by convention in config. | ai | |
| phantom-deps | phantom-dep:@eslint-sukka/eslint-plugin-react-jsx-a11y | AI (phantom-deps): Same-org ESLint plugin; loaded by convention in config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint plugin referenced in config files, not directly imported. | ai | |
| phantom-deps | phantom-dep:@eslint/compat | AI (phantom-deps): Framework-scoped ESLint compat package; loaded by convention in config. | ai | |
| phantom-deps | phantom-dep:@stylexjs/eslint-plugin | AI (phantom-deps): ESLint plugin referenced in config files, not directly imported. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 8.10.4 | 11 / 4 | |
| 8.10.3 | 11 / 5 | |
| 8.10.2 | 11 / 5 | |
| 8.10.1 | 11 / 5 | |
| 8.10.0 | 11 / 5 | |
| 8.9.4 | 11 / 5 | |
| 8.9.3 | 11 / 5 | |
| 8.9.2 | 11 / 5 | |
| 8.9.1 | 11 / 5 | |
| 8.9.0 | 9 / 4 | |
| 8.8.0 | 9 / 4 | |
| 8.7.1 | 9 / 4 | |
| 8.7.0 | 9 / 4 | |
| 8.6.5 | 9 / 4 | |
| 8.6.4 | 9 / 4 | |
| 8.6.1 | 9 / 4 | |
| 8.6.0 | 9 / 4 | |
| 8.5.0 | 10 / 3 | |
| 8.4.0 | 11 / 3 | |
| 8.3.0 | 11 / 3 | |
| 8.0.6 | 11 / 3 | |
| 8.0.4 | 11 / 3 | |
| 8.0.3 | 11 / 3 | |
| 8.0.2 | 11 / 3 | |
| 8.0.1 | 11 / 3 | |
| 8.0.0 | 11 / 3 |
v8.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.9.4
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.9.3
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.9.2
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.9.1
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.9.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.8.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.7.1
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.7.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.5
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.4
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.1
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.3.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.6
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.4
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.3
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.2
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
2 findingsMaintainer email 'https://skk.moe' uses domain 'https://skk.moe' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.