eslint-plugin-functional
ESLint rules to promote functional programming in TypeScript.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:ts-api-utils | AI (dependencies): ts-api-utils is a well-known TypeScript API utility package widely used in the TypeScript/ESLint ecosystem; not a security concern for this plugin. | ai | |
| dependencies | unvetted-dep:@typescript-eslint/utils | AI (dependencies): @typescript-eslint/utils is from the official typescript-eslint org and is a standard dependency for ESLint plugins targeting TypeScript. | ai | |
| dependencies | unvetted-dep:is-immutable-type | AI (dependencies): is-immutable-type is a companion package by the same author (Rebecca Stevens) used for TypeScript immutability analysis; legitimate dependency for this plugin. | ai | |
| dependencies | unvetted-dep:ts-declaration-location | AI (dependencies): ts-declaration-location is a small TypeScript utility package; legitimate dependency for this ESLint plugin's TypeScript analysis features. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 6 / 56 | |
| 9.0.5 | 6 / 57 | |
| 9.0.4 | 6 / 56 | |
| 9.0.3 | 6 / 56 | |
| 9.0.2 | 6 / 63 | |
| 9.0.1 | 6 / 64 | |
| 9.0.0 | 6 / 64 |
v10.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.