Snyk Code "not supported / not enabled" for the organization in CI

By Daniel Zoghalchali·Latchkey

Snyk Code (the SAST product) is a per-organization setting. If it is disabled in the Snyk org, snyk code test refuses to run and reports that Snyk Code is not supported or not enabled, regardless of a valid token.

What this error means

The Snyk step fails with "Snyk Code is not supported for this organization" or "Snyk Code is not enabled", even though authentication succeeded.

Snyk Code is not supported for org: your-org.
Enable Snyk Code under Settings > Snyk Code in the Snyk web UI.

Common causes

Snyk Code is off in org settings

The SAST feature is disabled for the Snyk organization, so code tests are not permitted.

The token belongs to the wrong org

The token authenticates to an org where Snyk Code is not enabled; the intended org differs.

How to fix it

Enable Snyk Code and target the right org

1. In the Snyk web UI, open Settings > Snyk Code and enable it.
2. Confirm the token belongs to that organization.
3. Set --org on the command if you manage multiple orgs.

- run: snyk code test --org=${{ vars.SNYK_ORG }}
  env:
    SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}

Verify plan entitlement

Confirm your Snyk plan includes Snyk Code (SAST); some tiers require it to be added before enablement.

How to prevent it

• Enable Snyk Code in org settings before adding the CI step.
• Pin --org so scans target the enabled organization.
• Confirm plan entitlement for SAST.

Frequently asked questions

Related guides

References

• GitHub Actions documentation