@ijlee2-frontend-configs/eslint-config-ember
Configuration for eslint (Ember)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted publisher with strong track record; no other risk signals; likely a CI environment change. | ai | |
| dependencies | unvetted-dep:eslint-plugin-qunit | AI (dependencies): eslint-plugin-qunit is a well-established QUnit linting plugin; stable false positive for this ESLint config package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Babel packages are runtime deps loaded by convention in ESLint configs, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-decorators | AI (phantom-deps): Babel plugin referenced by config convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint resolver referenced in config files by convention, not directly imported. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.4.3 | 15 / 5 | |
| 3.4.2 | 15 / 5 | |
| 3.4.1 | 15 / 5 | |
| 3.4.0 | 15 / 5 | |
| 3.3.0 | 15 / 5 | |
| 3.2.0 | 15 / 5 | |
| 3.1.1 | 15 / 5 | |
| 3.1.0 | 15 / 5 | |
| 3.0.1 | 15 / 5 | |
| 3.0.0 | 15 / 5 | |
| 2.6.1 | 15 / 5 | |
| 2.6.0 | 15 / 5 | |
| 2.5.0 | 15 / 5 | |
| 2.4.3 | 15 / 5 | |
| 2.4.2 | 15 / 5 | |
| 2.4.1 | 15 / 5 | |
| 2.4.0 | 15 / 5 |
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
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: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
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: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
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: ijlee2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.