@plugjs/eslint-plugin
Shared ESLint configurations and extras
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions CI/CD with SLSA provenance; this is the documented publish mechanism for this package. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-node | AI (phantom-deps): ESLint resolver plugins are referenced in config, not imported directly; expected pattern for eslint-plugin packages. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint resolver plugins are referenced in config, not imported directly; expected pattern for eslint-plugin packages. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 8 / 4 | |
| 0.7.1 | 8 / 4 | |
| 0.7.0 | 8 / 4 | |
| 0.6.17 | 8 / 4 | |
| 0.6.16 | 8 / 4 | |
| 0.6.15 | 8 / 4 | |
| 0.6.14 | 8 / 4 | |
| 0.6.13 | 8 / 4 | |
| 0.6.12 | 8 / 4 | |
| 0.6.11 | 8 / 4 | |
| 0.6.10 | 8 / 4 | |
| 0.6.9 | 8 / 4 | |
| 0.6.8 | 8 / 4 | |
| 0.6.7 | 8 / 4 | |
| 0.6.6 | 8 / 4 | |
| 0.6.5 | 8 / 4 | |
| 0.6.4 | 8 / 4 | |
| 0.6.3 | 8 / 4 | |
| 0.6.2 | 8 / 4 | |
| 0.6.1 | 8 / 4 | |
| 0.6.0 | 8 / 4 | |
| 0.5.24 | 8 / 4 | |
| 0.5.23 | 8 / 4 | |
| 0.5.22 | 8 / 4 | |
| 0.5.21 | 8 / 4 | |
| 0.5.20 | 8 / 4 | |
| 0.5.19 | 8 / 4 | |
| 0.5.18 | 8 / 4 | |
| 0.5.17 | 8 / 4 | |
| 0.5.16 | 8 / 4 | |
| 0.5.15 | 8 / 4 | |
| 0.5.14 | 8 / 4 | |
| 0.5.13 | 8 / 4 | |
| 0.5.12 | 8 / 4 | |
| 0.5.11 | 8 / 4 | |
| 0.5.10 | 8 / 4 | |
| 0.5.9 | 8 / 4 | |
| 0.5.8 | 8 / 4 | |
| 0.5.7 | 8 / 4 | |
| 0.5.6 | 8 / 4 | |
| 0.5.5 | 8 / 4 | |
| 0.5.4 | 8 / 4 | |
| 0.5.3 | 8 / 4 | |
| 0.5.2 | 8 / 4 | |
| 0.5.1 | 8 / 4 | |
| 0.5.0 | 8 / 4 | |
| 0.4.0 | 8 / 1 | |
| 0.3.43 | 8 / 1 | |
| 0.3.42 | 8 / 1 | |
| 0.3.41 | 8 / 1 | |
| 0.3.40 | 8 / 1 | |
| 0.3.39 | 8 / 1 | |
| 0.3.38 | 8 / 1 | |
| 0.3.37 | 8 / 1 | |
| 0.3.36 | 8 / 1 | |
| 0.3.35 | 8 / 1 | |
| 0.3.34 | 8 / 1 | |
| 0.3.33 | 8 / 1 | |
| 0.3.32 | 8 / 1 | |
| 0.3.31 | 8 / 1 | |
| 0.3.30 | 8 / 1 | |
| 0.3.29 | 8 / 1 | |
| 0.3.28 | 8 / 1 | |
| 0.3.27 | 8 / 1 | |
| 0.3.26 | 8 / 1 | |
| 0.3.25 | 8 / 1 | |
| 0.3.24 | 8 / 1 | |
| 0.3.23 | 8 / 1 | |
| 0.3.22 | 8 / 1 | |
| 0.3.21 | 8 / 1 | |
| 0.3.19 | 8 / 1 | |
| 0.3.18 | 8 / 1 | |
| 0.3.17 | 8 / 1 | |
| 0.3.16 | 8 / 1 | |
| 0.3.15 | 8 / 1 | |
| 0.3.14 | 8 / 1 | |
| 0.3.13 | 8 / 1 | |
| 0.3.12 | 8 / 1 | |
| 0.3.11 | 8 / 1 | |
| 0.3.10 | 8 / 1 | |
| 0.3.9 | 8 / 1 | |
| 0.3.8 | 8 / 1 | |
| 0.3.7 | 8 / 1 | |
| 0.3.6 | 8 / 1 | |
| 0.3.5 | 8 / 1 | |
| 0.3.4 | 8 / 1 | |
| 0.3.3 | 8 / 1 | |
| 0.3.2 | 8 / 1 | |
| 0.3.1 | 8 / 1 | |
| 0.3.0 | 8 / 1 |
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.