eslint-config-atomic
Eslint config used in atom-ide-community
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are official @eslint org packages replacing eslint-plugin-json; benign ecosystem migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with trusted publisher; no material changes from prior version; dormancy consistent with low-churn config package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-only-warn | AI (dependencies): Author's own fork (@aminya/eslint-plugin-only-warn); expected for this package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-optimize-regex | AI (dependencies): Author's own fork pinned to a specific commit hash; acceptable supply-chain risk. | ai | |
| dependencies | unvetted-dep:make-synchronous | AI (dependencies): Known utility dep used by this eslint config; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a common implicit runtime dep; stable false positive for this package. | ai | |
| npm-metadata | url-dep:eslint-plugin-optimize-regex | AI (npm-metadata): GitHub dep is pinned to a specific commit hash, mitigating swap risk for this package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): ESLint config packages declare deps for consumers; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-jsx | AI (phantom-deps): Framework-scoped babel plugin; loaded by convention in eslint config context. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-flow | AI (phantom-deps): Framework-scoped babel plugin; loaded by convention in eslint config context. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config re-exports/references deps without direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:typescript-eslint | AI (phantom-deps): ESLint config re-exports/references deps without direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:read-pkg-up | AI (phantom-deps): ESLint config re-exports/references deps without direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): ESLint config re-exports/references deps without direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:subsume | AI (phantom-deps): ESLint config re-exports/references deps without direct import; stable pattern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 29 / 24 | |
| 2.1.0 | 30 / 23 | |
| 2.0.5 | 29 / 23 | |
| 2.0.4 | 29 / 23 | |
| 2.0.3 | 29 / 23 | |
| 2.0.2 | 29 / 23 | |
| 2.0.1 | 29 / 23 | |
| 2.0.0 | 29 / 23 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.