eslint-config-sukka
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:eslint-plugin-paths | AI (dependencies): Small eslint plugin dependency; no malware indicators; stable for this config package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-autofix | AI (dependencies): Small eslint plugin dependency; no malware indicators; stable for this config package. | ai | |
| email-domain | unclaimed-email:https://skk.moe | AI (email-domain): skk.moe is the author's active personal site used as a URL in the author field, not an email domain; stable false positive for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance via Sigstore is a strong supply chain integrity signal; stable for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 8.10.4 | 21 / 9 | |
| 8.10.3 | 21 / 9 | |
| 8.10.2 | 21 / 9 | |
| 8.10.1 | 21 / 9 | |
| 8.10.0 | 21 / 9 | |
| 8.9.4 | 21 / 8 | |
| 8.9.3 | 21 / 8 | |
| 8.9.2 | 21 / 8 | |
| 8.9.1 | 21 / 8 | |
| 8.9.0 | 21 / 8 | |
| 8.8.0 | 21 / 8 | |
| 8.7.1 | 21 / 8 | |
| 8.7.0 | 21 / 8 | |
| 8.6.5 | 21 / 8 | |
| 8.6.4 | 22 / 8 | |
| 8.0.4 | 23 / 8 | |
| 8.0.3 | 23 / 8 | |
| 8.0.2 | 22 / 10 | |
| 8.0.0 | 22 / 10 |
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.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.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.