ember-eslint-parser
This is the eslint parser for ember's gjs and gts files (using `<template>`), and also for Handlebars (`.hbs`) template files.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Early placeholder 0.0.1 of a now-trusted, widely-downloaded package; not spam. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is intentional and backed by SLSA provenance attestation; stable for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Resolves TypeScript from a user-configured parser path; standard pattern for ESLint parsers supporting optional TS. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.14.4 | 8 / 23 | |
| 0.14.3 | 8 / 23 | |
| 0.14.2 | 8 / 23 | |
| 0.14.1 | 8 / 23 | |
| 0.14.0 | 8 / 23 | |
| 0.13.0 | 8 / 23 | |
| 0.12.1 | 8 / 23 | |
| 0.12.0 | 8 / 23 | |
| 0.11.3 | 8 / 23 | |
| 0.11.2 | 8 / 23 | |
| 0.11.1 | 9 / 21 | |
| 0.11.0 | 8 / 21 | |
| 0.10.0 | 8 / 21 | |
| 0.9.0 | 8 / 21 | |
| 0.8.0 | 8 / 20 | |
| 0.7.0 | 8 / 20 | |
| 0.6.0 | 8 / 20 | |
| 0.5.13 | 8 / 20 | |
| 0.5.12 | 8 / 20 | |
| 0.5.11 | 8 / 20 | |
| 0.5.10 | 7 / 20 | |
| 0.5.9 | 7 / 20 | |
| 0.5.8 | 7 / 20 | |
| 0.5.7 | 7 / 20 | |
| 0.5.6 | 7 / 20 | |
| 0.5.5 | 6 / 20 | |
| 0.5.4 | 5 / 20 | |
| 0.5.3 | 5 / 20 | |
| 0.5.2 | 5 / 20 | |
| 0.5.1 | 5 / 20 | |
| 0.5.0 | 5 / 20 | |
| 0.4.3 | 5 / 20 | |
| 0.4.2 | 5 / 20 | |
| 0.4.1 | 5 / 20 | |
| 0.4.0 | 6 / 19 | |
| 0.3.8 | 6 / 19 | |
| 0.3.7 | 6 / 19 | |
| 0.3.6 | 6 / 19 | |
| 0.3.5 | 6 / 18 | |
| 0.3.4 | 6 / 18 | |
| 0.3.3 | 6 / 18 | |
| 0.3.2 | 6 / 18 | |
| 0.3.1 | 6 / 18 | |
| 0.3.0 | 6 / 18 | |
| 0.2.6 | 6 / 17 | |
| 0.2.5 | 6 / 17 | |
| 0.2.4 | 6 / 17 | |
| 0.2.3 | 6 / 17 | |
| 0.2.2 | 6 / 17 | |
| 0.2.1 | 6 / 17 | |
| 0.2.0 | 6 / 15 | |
| 0.1.1 | 6 / 15 | |
| 0.1.0 | 6 / 12 | |
| 0.0.1 | 0 / 0 |
v0.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsMatched 6 signal(s), weighted score 7: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 0 code file(s), 255 bytes total.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.