use crate::common::{input_under_test, zizmor};

#[test]
fn test_caching_disabled_by_default() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-disabled-by-default.yml"
            ))
            .run()?,
        @"No findings to report. Good job! (1 suppressed)"
    );

    Ok(())
}

#[test]
fn test_caching_enabled_by_default() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-enabled-by-default.yml"
            ))
            .run()?,
        @"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:21:9
       |
     1 | on: release
       | ----------- generally used when publishing artifacts generated at runtime
    ...
    21 |         uses: Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    4 findings (1 ignored, 2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    ",
    );

    Ok(())
}

#[test]
fn test_caching_opt_in_boolean_toggle() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-opt-in-boolean-toggle.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:19:9
       |
     1 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    19 |           uses: actions/setup-dotnet@3e891b0cb619bf60e2c25674b222b8940e2c1c25
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    20 | /         with:
    21 | |           dotnet-version: "5.0.x"
    22 | |           cache: true
       | |_____________________- enables caching explicitly here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    4 findings (1 ignored, 2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#,
    );

    Ok(())
}

#[test]
fn test_caching_opt_in_expression() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-opt-in-expression.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:19:9
       |
     1 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    19 |           uses: astral-sh/setup-uv@38f3f104447c67c051c4a08e39b64a148898af3a
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    20 | /         with:
    21 | |           python-version: "3.12"
    22 | |           enable-cache: ${{ github.ref == 'refs/heads/main' }}
       | |______________________________________________________________- may enable caching here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    3 findings (1 ignored, 1 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#,
    );

    Ok(())
}

#[test]
fn test_caching_opt_in_multi_value_toggle() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-opt-in-multi-value-toggle.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:18:9
       |
     1 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    18 |           uses: actions/setup-java@8df1039502a15bceb9433410b1a100fbe190c53b
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    19 | /         with:
    20 | |           distribution: "zulu"
    21 | |           cache: "gradle"
    22 | |           java-version: "17"
       | |____________________________- enables caching explicitly here
       |
       = note: audit confidence → Low

    2 findings (1 suppressed): 0 informational, 0 low, 0 medium, 1 high
    "#,
    );

    Ok(())
}

#[test]
fn test_caching_opt_out() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/caching-opt-out.yml"))
            .run()?,
        @"No findings to report. Good job! (1 ignored, 2 suppressed)"
    );

    Ok(())
}

#[test]
fn test_no_cache_aware_steps() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/no-cache-aware-steps.yml"))
            .run()?,
        @"No findings to report. Good job! (1 ignored, 2 suppressed)"
    );

    Ok(())
}

#[test]
fn test_workflow_tag_trigger() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/workflow-tag-trigger.yml"))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:23:9
       |
     1 | / on:
     2 | |   push:
     3 | |     tags:
     4 | |       - "**"
       | |____________- generally used when publishing artifacts generated at runtime
    ...
    23 |           uses: Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    4 findings (1 ignored, 2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#
    );

    Ok(())
}

#[test]
fn test_caching_opt_in_boolish_toggle() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-opt-in-boolish-toggle.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:17:9
       |
     4 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    17 |           uses: PyO3/maturin-action@ea5bac0f1ccd0ab11c805e2b804bfcb65dac2eab # v1
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    18 | /         with:
    19 | |           target: ${{ matrix.platform.target }}
    20 | |           args: --release --out dist
    21 | |           sccache: "true"
       | |__________________________- enables caching explicitly here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    2 findings (1 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#,
    );

    Ok(())
}

#[test]
fn test_publisher_step() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/publisher-step.yml"))
            .run()?,
        @"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:23:9
       |
    23 |         uses: Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
    ...
    30 |         uses: softprops/action-gh-release@01570a1f39cb168c169c802c3bceb9e93fb10974 # zizmor: ignore[superfluous-actions]
       |         -------------------------------------------------------------------------- runtime artifacts usually published here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    3 findings (1 ignored, 1 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "
    );

    Ok(())
}

/// Bug #343: setup-go's caching behavior was not modeled as opt-out.
///
/// See: <https://github.com/zizmorcore/zizmor/pull/343>
#[test]
fn test_issue_343() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-343-repro.yml"))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:28:9
       |
     5 | / on:
     6 | |   push:
     7 | |     tags:
     8 | |       - "v*.*.*"
       | |________________- generally used when publishing artifacts generated at runtime
    ...
    28 |           uses: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c # v6.1.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:34:9
       |
     5 | / on:
     6 | |   push:
     7 | |     tags:
     8 | |       - "v*.*.*"
       | |________________- generally used when publishing artifacts generated at runtime
    ...
    34 |           uses: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c # v6.1.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    35 | /         with:
    36 | |           go-version: stable
    37 | |           cache: true
    38 | |
    39 | |       # Finding because setup enables cache explicitly
       | |______________________________________________________- enables caching explicitly here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:41:9
       |
     5 | / on:
     6 | |   push:
     7 | |     tags:
     8 | |       - "v*.*.*"
       | |________________- generally used when publishing artifacts generated at runtime
    ...
    41 |           uses: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c # v6.1.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    42 | /         with:
    43 | |           go-version: stable
    44 | |           cache: "true"
       | |________________________- enables caching explicitly here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    5 findings (2 suppressed, 3 unsafe fixes): 0 informational, 0 low, 0 medium, 3 high
    "#
    );

    Ok(())
}

#[test]
fn test_caching_not_configurable() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/caching-not-configurable.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:23:9
       |
     1 | / on:
     2 | |   push:
     3 | |     tags:
     4 | |       - "**"
       | |____________- generally used when publishing artifacts generated at runtime
    ...
    23 |           uses: Mozilla-Actions/sccache-action@054db53350805f83040bf3e6e9b8cf5a139aa7c9
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ always restores from cache
       |
       = note: audit confidence → Low

    4 findings (1 ignored, 2 suppressed): 0 informational, 0 low, 0 medium, 1 high
    "#
    );

    Ok(())
}

#[test]
fn test_workflow_release_branch_trigger() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/workflow-release-branch-trigger.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:22:9
       |
     1 | / on:
     2 | |   push:
     3 | |     branches:
     4 | |       - "release-v2.0.0"
       | |________________________- generally used when publishing artifacts generated at runtime
    ...
    22 |           uses: Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    4 findings (1 ignored, 2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#
    );

    Ok(())
}

/// Bug #378: docker/build-push-action should not be considered a publishing
/// sink when `push: false`.
///
/// See: <https://github.com/zizmorcore/zizmor/issues/378>
#[test]
fn test_issue_378() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-378-repro.yml"))
            .run()?,
        @"No findings to report. Good job! (1 suppressed)"
    );

    Ok(())
}

/// See: <https://github.com/zizmorcore/zizmor/issues/642>
#[test]
fn test_issue_642() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-642-repro.yml"))
            .run()?,
        @"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:15:9
       |
    15 |           uses: docker/setup-buildx-action@6524bf65af31da8d45b59e8c27de4bd072b392f5
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    16 | /         with:
    17 | |           cache-binary: true
    18 | |           version: latest
       | |_________________________- enables caching explicitly here
    ...
    21 |           uses: docker/build-push-action@48aba3b46d1b1fec4febb7c5d0c644b249a11355
       |           ----------------------------------------------------------------------- runtime artifacts usually published here
       |
       = note: audit confidence → Low

    2 findings (1 suppressed): 0 informational, 0 low, 0 medium, 1 high
    "
    );

    Ok(())
}

// Bug #1081: setup-uv's caching analysis was inverted.
//
// See: <https://github.com/zizmorcore/zizmor/issues/1081>
#[test]
fn test_issue_1081() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-1081-repro.yml"))
            .run()?,
        @"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:15:9
       |
     5 | on: release
       | ----------- generally used when publishing artifacts generated at runtime
    ...
    15 |       - uses: astral-sh/setup-uv@d9e0f98d3fc6adb07d1e3d37f3043649ddad06a1 # v6.5.0
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:18:9
       |
     5 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    18 |         - uses: astral-sh/setup-uv@d9e0f98d3fc6adb07d1e3d37f3043649ddad06a1 # v6.5.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    19 | /         with:
    20 | |           enable-cache: true
       | |____________________________- enables caching explicitly here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    3 findings (1 suppressed, 2 unsafe fixes): 0 informational, 0 low, 0 medium, 2 high
    "
    );

    Ok(())
}

/// Bug #1152: Changes to setup-node v5's caching behavior.
///
/// See: <https://github.com/zizmorcore/zizmor/issues/1152>
#[test]
fn test_issue_1152() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-1152-repro.yml"))
            .run()?,
        @"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:16:9
       |
     5 | on: release
       | ----------- generally used when publishing artifacts generated at runtime
    ...
    16 |         uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low

    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:20:9
       |
     5 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    20 |           uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    21 | /         with:
    22 | |           package-manager-cache: true
       | |_____________________________________- enables caching explicitly here
       |
       = note: audit confidence → Low

    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:42:9
       |
     5 | on: release
       | ----------- generally used when publishing artifacts generated at runtime
    ...
    42 |       - uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low

    4 findings (1 suppressed): 0 informational, 0 low, 0 medium, 3 high
    "
    );

    Ok(())
}

/// Bug #1485: `cache: ""` should not be treated as opt-in for caching.
///
/// See: <https://github.com/zizmorcore/zizmor/issues/1485>
#[test]
fn test_issue_1485() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-1485-repro.yml"))
            .run()?,
        @"No findings to report. Good job! (2 suppressed)"
    );

    Ok(())
}

/// Tests for `ramsey/composer-install`'s caching behavior.
#[test]
fn test_ramsey_composer_install_action() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/ramsey-composer-install.yml"
            ))
            .run()?,
        @"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:13:9
       |
     1 | on: release
       | ----------- generally used when publishing artifacts generated at runtime
    ...
    13 |       - uses: ramsey/composer-install@3cf229dc2919194e9e36783941438d17239e8520 # 3.1.1
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low

    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:15:9
       |
     1 |   on: release
       |   ----------- generally used when publishing artifacts generated at runtime
    ...
    15 |         - uses: ramsey/composer-install@3cf229dc2919194e9e36783941438d17239e8520 # 3.1.1
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    16 | /         with:
    17 | |           # NOT OK: caching explicitly enabled
    18 | |           ignore-cache: false
       | |_____________________________- enables caching explicitly here
       |
       = note: audit confidence → Low

    3 findings (1 suppressed): 0 informational, 0 low, 0 medium, 2 high
    "
    );

    Ok(())
}

/// Tests that we properly handle `on: ... release:` style triggers,
/// i.e. where `release:` is a key rather than a bare trigger name.
#[test]
fn test_workflow_release_trigger_object() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/workflow-release-trigger-object.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:23:9
       |
     1 | / on:
     2 | |   push:
     3 | |     branches:
     4 | |       - "main"
     5 | |   release:
       | |__________- generally used when publishing artifacts generated at runtime
    ...
    23 |           uses: Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    4 findings (1 ignored, 2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#
    );

    Ok(())
}

// See: <https://github.com/zizmorcore/zizmor/issues/1940>
#[test]
fn test_issue_1940() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/issue-1940-repro.yml")).run()?,
        @r#"No findings to report. Good job! (2 suppressed)"#);

    Ok(())
}

#[test]
fn test_trigger_heuristics_tag_only() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test("cache-poisoning/trigger-heuristics/tag-only.yml"))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:16:9
       |
     3 | / on:
     4 | |   push:
     5 | |     branches:
     6 | |       - master
     7 | |     tags:
     8 | |       - "*"
       | |___________- generally used when publishing artifacts generated at runtime
    ...
    16 |         - uses: PyO3/maturin-action@e83996d129638aa358a18fbd1dfb82f0b0fb5d3b # v1.51.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    17 | /         with:
    18 | |           # this is the opposite of #1940: caching is explicitly enabled here,
    19 | |           # but *only* for tag events, which we consider unsafe becaue we assume that
    20 | |           # tag events correspond to releases.
    21 | |           sccache: ${{ startsWith(github.ref, 'refs/tags/') }}
       | |_______________________________________________________________- enables caching explicitly here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    3 findings (2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#
    );

    Ok(())
}

#[test]
fn test_trigger_heuristics_tag_and_release() -> anyhow::Result<()> {
    insta::assert_snapshot!(
        zizmor()
            .input(input_under_test(
                "cache-poisoning/trigger-heuristics/tag-and-release.yml"
            ))
            .run()?,
        @r#"
    error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
      --> @@INPUT@@:17:9
       |
     3 | / on:
     4 | |   push:
     5 | |     branches:
     6 | |       - master
     7 | |     tags:
     8 | |       - "*"
     9 | |   release:
       | |__________- generally used when publishing artifacts generated at runtime
    ...
    17 |         - uses: PyO3/maturin-action@e83996d129638aa358a18fbd1dfb82f0b0fb5d3b # v1.51.0
       |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this step
    18 | /         with:
    19 | |           # we would consider this safe *if* there was only a tag trigger for this workflow,
    20 | |           # but since there's also a release trigger we can't assert that all release
    21 | |           # events will also be tag events.
    22 | |           sccache: ${{ !startsWith(github.ref, 'refs/tags/') }}
       | |________________________________________________________________- may enable caching here
       |
       = note: audit confidence → Low
       = note: this finding has an auto-fix

    3 findings (2 suppressed, 1 unsafe fixes): 0 informational, 0 low, 0 medium, 1 high
    "#
    );

    Ok(())
}
