@sap-ux/eslint-plugin-fiori-tools
Custom linting plugin for Fiori tools apps
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-plugin-fiori-custom | AI (phantom-deps): ESLint plugin deps are referenced in config files, not imported directly; stable false positive for this package type. | ai | |
| provenance | publisher-changed | AI (provenance): SAP org migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this package going forward. | ai | |
| dependencies | unvetted-dep:@sap-ux/odata-vocabularies | AI (dependencies): Same SAP UX org scope; stable sibling dependency. | ai | |
| dependencies | unvetted-dep:@xml-tools/ast | AI (dependencies): Known SAP/xml-tools ecosystem package; stable dependency for this ESLint plugin. | ai | |
| dependencies | unvetted-dep:@sap-ux/odata-annotation-core | AI (dependencies): Same SAP UX org scope; stable sibling dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/vocabularies-types | AI (dependencies): Same SAP UX org scope; stable sibling dependency. | ai | |
| dependencies | unvetted-dep:@sap-ux/odata-entity-model | AI (dependencies): Same SAP UX org scope; stable sibling dependency. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): ESLint plugin config tooling; yaml referenced in config files, not a runtime import concern. | ai | |
| phantom-deps | phantom-dep:@sap-ux/vocabularies-types | AI (phantom-deps): Same-org SAP monorepo sibling; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this plugin package. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): Framework-scoped ESLint package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Peer/framework-scoped; loaded by @babel/eslint-parser at runtime by convention. | ai | |
| phantom-deps | phantom-dep:requireindex | AI (phantom-deps): Used in index generation config; stable false positive for this plugin. | ai | |
| phantom-deps | phantom-dep:@sap-ux/odata-entity-model | AI (phantom-deps): Same-org SAP monorepo sibling; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@sap-ux/odata-vocabularies | AI (phantom-deps): Same-org SAP monorepo sibling; phantom-dep heuristic false positive. | ai |
Versions (showing 51 of 99)
| Version | Deps | Published |
|---|---|---|
| 10.6.1 | 25 / 6 | |
| 10.6.0 | 25 / 6 | |
| 10.5.4 | 25 / 6 | |
| 10.5.3 | 25 / 6 | |
| 10.5.1 | 25 / 6 | |
| 10.5.0 | 25 / 6 | |
| 10.4.1 | 24 / 6 | |
| 10.4.0 | 24 / 6 | |
| 10.3.0 | 24 / 5 | |
| 10.2.2 | 24 / 5 | |
| 10.2.1 | 24 / 5 | |
| 10.2.0 | 24 / 5 | |
| 10.1.2 | 24 / 5 | |
| 10.1.1 | 24 / 5 | |
| 10.0.6 | 24 / 5 | |
| 10.0.5 | 24 / 5 | |
| 10.0.4 | 24 / 5 | |
| 10.0.3 | 24 / 5 | |
| 10.0.2 | 24 / 5 | |
| 10.0.1 | 24 / 5 | |
| 10.0.0 | 24 / 5 | |
| 9.13.0 | 24 / 4 | |
| 9.12.3 | 24 / 5 | |
| 9.12.2 | 24 / 5 | |
| 9.12.1 | 24 / 5 | |
| 9.12.0 | 24 / 5 | |
| 9.11.7 | 24 / 5 | |
| 9.11.6 | 24 / 5 | |
| 9.11.5 | 24 / 5 | |
| 9.11.4 | 24 / 5 | |
| 9.11.3 | 24 / 5 | |
| 9.11.2 | 24 / 5 | |
| 9.11.1 | 24 / 5 | |
| 9.11.0 | 24 / 5 | |
| 9.10.5 | 24 / 5 | |
| 9.10.4 | 24 / 5 | |
| 9.10.3 | 24 / 5 | |
| 9.10.2 | 24 / 5 | |
| 9.10.1 | 24 / 5 | |
| 9.10.0 | 24 / 5 | |
| 9.9.4 | 24 / 5 | |
| 9.9.3 | 24 / 5 | |
| 9.9.2 | 24 / 5 | |
| 9.9.1 | 24 / 5 | |
| 9.9.0 | 24 / 5 | |
| 9.8.0 | 24 / 5 | |
| 9.7.8 | 24 / 5 | |
| 9.7.7 | 24 / 5 | |
| 9.7.6 | 24 / 5 | |
| 9.7.5 | 24 / 5 | |
| 9.7.4 | 24 / 5 |
v10.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.7
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.6
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.8
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.