eslint-plugin-unicorn
More than 100 powerful ESLint rules
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() in expiring-todo-comments.js is standard Proxy handler usage (forwarding get trap), not obfuscation. This pattern is expected in ESLint rule implementations. | ai |
Versions (showing 51 of 118)
| Version | Deps | Published |
|---|---|---|
| 64.0.0 | 16 / 31 | |
| 63.0.0 | 16 / 33 | |
| 62.0.0 | 18 / 33 | |
| 61.0.2 | 18 / 31 | |
| 61.0.1 | 18 / 31 | |
| 61.0.0 | 18 / 31 | |
| 60.0.0 | 18 / 31 | |
| 59.0.1 | 17 / 32 | |
| 59.0.0 | 17 / 32 | |
| 58.0.0 | 17 / 32 | |
| 57.0.0 | 16 / 33 | |
| 56.0.1 | 16 / 31 | |
| 56.0.0 | 16 / 31 | |
| 55.0.0 | 16 / 31 | |
| 54.0.0 | 16 / 30 | |
| 53.0.0 | 16 / 30 | |
| 52.0.0 | 16 / 29 | |
| 51.0.1 | 16 / 29 | |
| 51.0.0 | 16 / 29 | |
| 50.0.1 | 16 / 28 | |
| 50.0.0 | 16 / 28 | |
| 49.0.0 | 14 / 28 | |
| 48.0.1 | 15 / 28 | |
| 48.0.0 | 15 / 28 | |
| 47.0.0 | 16 / 28 | |
| 46.0.1 | 16 / 28 | |
| 46.0.0 | 16 / 28 | |
| 45.0.2 | 16 / 28 | |
| 45.0.1 | 16 / 28 | |
| 45.0.0 | 16 / 28 | |
| 44.0.2 | 14 / 27 | |
| 44.0.1 | 14 / 27 | |
| 44.0.0 | 14 / 27 | |
| 43.0.2 | 14 / 26 | |
| 43.0.1 | 14 / 26 | |
| 43.0.0 | 14 / 26 | |
| 42.0.0 | 14 / 26 | |
| 41.0.1 | 14 / 26 | |
| 41.0.0 | 14 / 26 | |
| 40.1.0 | 14 / 25 | |
| 40.0.0 | 14 / 25 | |
| 39.0.0 | 15 / 24 | |
| 38.0.1 | 15 / 22 | |
| 38.0.0 | 15 / 22 | |
| 37.0.1 | 15 / 22 | |
| 37.0.0 | 15 / 22 | |
| 36.0.0 | 12 / 22 | |
| 35.0.0 | 12 / 22 | |
| 34.0.1 | 12 / 22 | |
| 34.0.0 | 12 / 22 | |
| 33.0.1 | 13 / 22 |
v64.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v63.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v62.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v58.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v54.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v53.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.