@redhat-cloud-services/eslint-config-redhat-cloud-services@3.3.13
Recommended eslint configuration used in cloud.redhat.com frontend apps.
AI Security Review
scanned 15h ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the entrypoint configures ESLint using its declared parser and plugins. The required rule, utility, and parser source paths show linting and parsing behavior, with no concrete attack behavior identified.
Decision evidence
public snapshot- package.json declares no scripts and points to index.js, which builds an ESLint configuration from parser and lint plugins.
- The inspected required rule modules export named ESLint rules through createRule; their behavior is linting rather than package installation or unrelated system actions.
- The inspected parser and utility modules handle parsing and ESLint configuration; inspected dependency manifests show no install lifecycle scripts.
Source & flagged code
8 flagged · loading sourcepackage.json declares no scripts and points to index.js, which builds an ESLint configuration from parser and lint plugins.
package.jsonView on unpkg · L10package.json declares no scripts and points to index.js, which builds an ESLint configuration from parser and lint plugins.
index.jsView on unpkg · L27Findings
Affected versions and remediation
This report applies to @redhat-cloud-services/eslint-config-redhat-cloud-services@3.3.13.
See all versions of @redhat-cloud-services/eslint-config-redhat-cloud-services for other recorded verdicts.
- Review the evidence and your use of @redhat-cloud-services/eslint-config-redhat-cloud-services@3.3.13 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.