@eslint-sukka/node
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 domain; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped ESLint config package; Levenshtein match to 'zod' is a false positive with no brand/functionality overlap. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 8.10.4 | 3 / 1 | |
| 8.10.3 | 3 / 1 | |
| 8.10.2 | 3 / 1 | |
| 8.10.1 | 3 / 1 | |
| 8.10.0 | 3 / 1 | |
| 8.9.4 | 3 / 1 | |
| 8.9.3 | 3 / 1 | |
| 8.9.2 | 3 / 1 | |
| 8.9.1 | 3 / 1 | |
| 8.9.0 | 3 / 1 | |
| 8.8.0 | 3 / 1 | |
| 8.7.1 | 3 / 1 | |
| 8.7.0 | 3 / 1 | |
| 8.6.5 | 3 / 1 | |
| 8.6.4 | 3 / 1 | |
| 8.6.1 | 3 / 1 | |
| 8.6.0 | 3 / 1 | |
| 8.5.0 | 3 / 1 | |
| 8.4.0 | 3 / 1 | |
| 8.3.0 | 3 / 1 | |
| 8.2.0 | 3 / 1 | |
| 8.1.0 | 3 / 1 | |
| 8.0.6 | 3 / 1 | |
| 8.0.5 | 3 / 1 | |
| 8.0.4 | 3 / 1 | |
| 8.0.3 | 3 / 1 | |
| 8.0.2 | 3 / 1 | |
| 8.0.1 | 3 / 1 | |
| 8.0.0 | 3 / 1 |
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.2.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.1.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.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.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.