@darajs/eslint-config
Dara ESLint configuration
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@typescript/native | AI (phantom-deps): Config-only eslint package; deps are consumed via config, not imports. | ai | |
| phantom-deps | phantom-dep:@vitest/eslint-plugin | AI (phantom-deps): Framework-scoped plugin loaded by convention, not direct import. | ai | |
| dependencies | unvetted-dep:@typescript/native | AI (dependencies): Alias resolves to official typescript package on npm. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI with SLSA provenance attestation; legitimate CI/CD migration for causalens/dara monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 200 versions in registry; dormancy followed by CI-attested publish with no code changes is consistent with a tooling/pipeline update, not takeover. | ai | |
| phantom-deps | phantom-dep:eslint-config-airbnb | AI (phantom-deps): ESLint config referenced in extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint plugin referenced in config extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config referenced in extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jsx-a11y | AI (phantom-deps): ESLint plugin referenced in config extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): ESLint config packages reference plugins/configs in extends/rules, not imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint parser referenced in config; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint plugin referenced in config extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint plugin referenced in config extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint resolver referenced in config; standard for config packages. | ai | |
| phantom-deps | phantom-dep:@darajs/prettier-config | AI (phantom-deps): Org-scoped config referenced in prettier field; standard for config packages. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Referenced in prettier field; stable pattern for config packages. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Peer dependency for TypeScript projects; referenced in config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jest | AI (phantom-deps): ESLint plugin referenced in config extends; standard for config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): ESLint plugin referenced in config extends; standard for config packages. | ai |
Versions (showing 55 of 155)
| Version | Deps | Published |
|---|---|---|
| 1.16.14 | 14 / 0 | |
| 1.16.13 | 14 / 0 | |
| 1.16.12 | 14 / 0 | |
| 1.16.11 | 14 / 0 | |
| 1.16.10 | 14 / 0 | |
| 1.16.9 | 14 / 0 | |
| 1.16.8 | 14 / 0 | |
| 1.16.7 | 14 / 0 | |
| 1.16.6 | 14 / 0 | |
| 1.16.5 | 14 / 0 | |
| 1.16.4 | 14 / 0 | |
| 1.16.3 | 14 / 0 | |
| 1.16.2 | 14 / 0 | |
| 1.16.1 | 14 / 0 | |
| 1.16.0 | 14 / 0 | |
| 1.15.7 | 14 / 0 | |
| 1.15.6 | 14 / 0 | |
| 1.15.5 | 14 / 0 | |
| 1.15.4 | 14 / 0 | |
| 1.15.3 | 14 / 0 | |
| 1.15.2 | 14 / 0 | |
| 1.15.1 | 14 / 0 | |
| 1.15.0 | 14 / 0 | |
| 1.14.9 | 14 / 0 | |
| 1.14.8 | 14 / 0 | |
| 1.14.7 | 14 / 0 | |
| 1.14.6 | 14 / 0 | |
| 1.14.5 | 14 / 0 | |
| 1.14.4 | 14 / 0 | |
| 1.14.3 | 14 / 0 | |
| 1.14.2 | 14 / 0 | |
| 1.14.1 | 14 / 0 | |
| 1.14.0 | 14 / 0 | |
| 1.13.1 | 14 / 0 | |
| 1.13.0 | 14 / 0 | |
| 1.12.7 | 14 / 0 | |
| 1.12.6 | 14 / 0 | |
| 1.12.5 | 14 / 0 | |
| 1.12.4 | 14 / 0 | |
| 1.12.3 | 14 / 0 | |
| 1.12.2 | 14 / 0 | |
| 1.12.1 | 14 / 0 | |
| 1.11.5 | 14 / 0 | |
| 1.11.4 | 14 / 0 | |
| 1.11.3 | 14 / 0 | |
| 1.11.2 | 14 / 0 | |
| 1.10.3 | 14 / 0 | |
| 1.10.2 | 14 / 0 | |
| 1.10.1 | 14 / 0 | |
| 1.10.0 | 14 / 0 | |
| 1.9.6 | 14 / 0 | |
| 1.9.5 | 14 / 0 | |
| 1.9.4 | 14 / 0 | |
| 1.9.3 | 14 / 0 | |
| 1.9.2 | 14 / 0 |
v1.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.