eslint-plugin-import-lite
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are established eslint/typescript-eslint ecosystem packages; dep swap is a normal refactor. | ai | |
| email-domain | unclaimed-email:https://github.com/9romise | AI (email-domain): Author field contains a GitHub URL, not an email address; domain-hijack risk does not apply. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 0 / 21 | |
| 0.5.2 | 0 / 20 | |
| 0.5.1 | 0 / 19 | |
| 0.5.0 | 0 / 19 | |
| 0.4.0 | 0 / 17 | |
| 0.3.1 | 0 / 17 | |
| 0.3.0 | 2 / 15 | |
| 0.2.0 | 2 / 15 | |
| 0.1.1 | 1 / 14 | |
| 0.1.0 | 1 / 14 |
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
2 findingsMaintainer email 'https://github.com/9romise' uses domain 'https://github.com/9romise' 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.
v0.5.1
2 findingsMaintainer email 'https://github.com/9romise' uses domain 'https://github.com/9romise' 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.
v0.5.0
2 findingsMaintainer email 'https://github.com/9romise' uses domain 'https://github.com/9romise' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsMaintainer email 'https://github.com/9romise' uses domain 'https://github.com/9romise' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsMaintainer email 'https://github.com/9romise' uses domain 'https://github.com/9romise' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vida0905.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vida0905.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.