← Home

eslint-plugin-functional

npm Repository Homepage

ESLint rules to promote functional programming in TypeScript.

4
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jonaskellorebeccastevens

Keywords

eslinteslint pluginfpfunctionalfunctional programmingimmutabilityimmutable

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 4 of 4)

Version Deps Published
9.0.5 6 / 57
9.0.4 6 / 56
9.0.3 6 / 56
9.0.2 6 / 63

v9.0.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v9.0.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v9.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.