@eagleoutice/flowr - v2.16.3
    Preparing search index...

    One step of R CMD check (a checking ... line of its log) and the linting rules covering it.

    interface ConformanceEntry {
        adds?: string;
        book: RPackagesSection;
        check: string;
        level: ConformanceLevel;
        line: number;
        note?: string;
        options?: readonly string[];
        rules: readonly (
            | "unused-import"
            | "deprecated-functions"
            | "file-path-validity"
            | "seeded-randomness"
            | "absolute-file-paths"
            | "unused-definitions"
            | "naming-convention"
            | "network-functions"
            | "dataframe-access-validation"
            | "dead-code"
            | "useless-loop"
            | "problematic-inputs"
            | "stop-call"
            | "roxygen-arguments"
            | "software-has-license"
            | "software-has-tests"
            | "no-leaked-credentials"
            | "undefined-symbol"
            | "syntactically-valid"
            | "unclosed-connection"
            | "unescaped-arguments"
            | "namespace-access"
            | "class-string-comparison"
            | "description-metadata"
            | "documentation-mismatch"
            | "non-ascii-code"
            | "true-false-abbreviation"
            | "bogus-return"
            | "package-hooks"
            | "global-environment-modification"
            | "namespace-tampering"
            | "s3-method-consistency"
            | "foreign-function-calls"
            | "dependency-declaration"
            | "call-arguments"
            | "package-structure"
            | "compiled-code"
            | "package-metafiles"
            | "rd-files"
            | "package-data"
            | "package-runtime"
        )[];
    }
    Index
    adds?: string

    what flowR reports beyond the step

    the section of the R Packages book describing the step

    check: string

    the step, as R CMD check names it in its log (checking <step> ...)

    line: number

    the line of CmdCheckSource that starts the step

    note?: string

    what flowR leaves out, or how it decides what R finds out by building or running the package

    options?: readonly string[]

    the configuration options () that tune what flowR reports for the step

    rules: readonly (
        | "unused-import"
        | "deprecated-functions"
        | "file-path-validity"
        | "seeded-randomness"
        | "absolute-file-paths"
        | "unused-definitions"
        | "naming-convention"
        | "network-functions"
        | "dataframe-access-validation"
        | "dead-code"
        | "useless-loop"
        | "problematic-inputs"
        | "stop-call"
        | "roxygen-arguments"
        | "software-has-license"
        | "software-has-tests"
        | "no-leaked-credentials"
        | "undefined-symbol"
        | "syntactically-valid"
        | "unclosed-connection"
        | "unescaped-arguments"
        | "namespace-access"
        | "class-string-comparison"
        | "description-metadata"
        | "documentation-mismatch"
        | "non-ascii-code"
        | "true-false-abbreviation"
        | "bogus-return"
        | "package-hooks"
        | "global-environment-modification"
        | "namespace-tampering"
        | "s3-method-consistency"
        | "foreign-function-calls"
        | "dependency-declaration"
        | "call-arguments"
        | "package-structure"
        | "compiled-code"
        | "package-metafiles"
        | "rd-files"
        | "package-data"
        | "package-runtime"
    )[]