@sap-cloud-sdk/eslint-config
eslint config for the SAP Cloud SDK
Supply chain provenance
Status for the latest visible version.
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): eslint-plugin-import-x is a well-known fork/replacement for eslint-plugin-import; swap is intentional and benign. | ai | |
| dependencies | unvetted-dep:eslint-plugin-regex | AI (dependencies): eslint-plugin-regex is a legitimate ESLint plugin for regex-based linting rules; its use in an ESLint config package is expected and benign across all versions. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config packages reference plugins/parsers by string name in config objects, not via require(). This is the standard pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint config packages reference plugins/parsers by string name in config objects, not via require(). This is the standard pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config packages reference parsers by string name in config objects, not via require(). This is the standard pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config packages reference resolvers by string name in config objects, not via require(). This is the standard pattern; not a real phantom dep. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 10 / 0 | |
| 4.6.0 | 11 / 0 | |
| 4.5.1 | 11 / 0 | |
| 4.5.0 | 11 / 0 | |
| 4.4.0 | 11 / 0 | |
| 4.3.1 | 11 / 0 | |
| 4.3.0 | 11 / 0 | |
| 4.2.0 | 11 / 0 | |
| 4.1.2 | 11 / 0 | |
| 4.1.1 | 11 / 0 | |
| 4.1.0 | 11 / 0 | |
| 4.0.2 | 11 / 0 | |
| 4.0.1 | 11 / 0 | |
| 4.0.0 | 11 / 0 |
v4.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marikaner) than the most recent previously approved version (deekshas8) on 2025-03-18, but marikaner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marikaner) than the most recent previously approved version (deekshas8) on 2025-03-05, but marikaner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.