[{"_1":2,"_164":-5,"_165":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_154":155},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_71":72,"_80":-7,"_81":-7,"_82":-7,"_83":-7,"_84":-5,"_85":-5,"_86":11,"_87":11,"_65":88,"_146":11,"_117":60,"_147":116,"_148":64,"_31":32,"_149":11,"_150":17,"_151":43,"_152":-5,"_153":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_56":57,"_58":30,"_59":60,"_61":62,"_63":64,"_65":66,"_67":45,"_68":57,"_69":54,"_70":17},"content_type","image","creator",2520828,"digest","sha256:f6e004193c9d21a6134ff5b173a34d68b501d8848d30c7fbc278e5f862077281","full_size",6754381,"id",927905051,"images",[39],{"_40":41,"_31":32,"_42":43,"_44":45,"_46":47,"_48":49,"_50":43,"_51":-5,"_52":34,"_53":54,"_55":-5},"architecture","arm64","features","","last_pulled","2026-09-18T03:46:25.130913251Z","last_pushed","2025-07-02T21:28:07.81590571Z","os","linux","os_features","os_version","size","status","active","variant","last_updated","2025-07-02T21:28:07.978318Z","last_updater","last_updater_username","simonkowallik","media_type","application/vnd.docker.container.image.v1+json","name","apiserver-arm64","repository",18806161,"tag_last_pulled","tag_last_pushed","tag_status","v2","tagImages",[73],{"_40":41,"_31":32,"_42":43,"_44":45,"_46":47,"_74":75,"_48":49,"_50":43,"_51":-5,"_52":34,"_53":54,"_55":-5},"layers",[76],{"_31":77,"_52":34,"_78":79},"sha256:839a0d369d86f09053c96accaba01e3d1165ccbf4e0cafc369deb644214b2c78","instruction","apko","layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_89":90,"_101":102,"_103":104,"_105":106,"_107":11,"_56":108,"_109":110,"_111":112,"_63":116,"_117":60,"_118":119,"_120":28,"_121":122,"_53":122,"_123":54,"_124":-5,"_125":126,"_127":128,"_129":11,"_130":60,"_131":132,"_137":11,"_138":139,"_143":60,"_144":145},"categories",[91,95,98],{"_63":92,"_93":94},"Networking","slug","networking",{"_63":96,"_93":97},"Languages & frameworks","languages-and-frameworks",{"_63":99,"_93":100},"Integration & delivery","integration-and-delivery","content_types",[28],"date_registered","2022-12-18T11:34:40.189437Z","description"," irulescan - security analyzer for iRules","is_private","2025-07-06T11:47:48.537917Z","last_modified","2025-07-02T22:11:07.224375Z","media_types",[62,113,114,115],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","irulescan","namespace","pull_count",1792,"repository_type","star_count",1,"status_description","source","collaborator_count",0,"full_description","

\n\n $\"irulescan\"$ \n\n
\n security analyzer for iRules\n

\n\n---\n\n

\n\n $\"test\"$ \n\n\n $\"container$ \n\n\n $\"releases\"$ \n\n

\n\n`irulescan` is a tool to scan iRules for unexpected/unsafe expressions that may have undesirable effects like double substitution and additional issues.\n\n`irulescan` would not exist without [tclscan](https://github.com/aidanhs/tclscan).\n\nIt is available as a docker/container image as well as a Github Action [`irulescan-action`](https://github.com/marketplace/actions/irules-security-scan).\n\n## Usage\n\nIt is easiest to use irulescan as a container to scan your iRules, available via [docker hub](https://hub.docker.com/r/simonkowallik/irulescan) as well as [ghcr.io](https://github.com/simonkowallik/irulescan/pkgs/container/irulescan).\n\nThe container will recursively scan files in the `/scandir` directory within the container and return results in JSON format.\nOnly files with the (case insensitive) file extensions `.tcl`, `.irul` and `.irule` will be scanned unless overwritten by environment variable `IRULESCAN_FILE_EXTENSIONS`.\n\n### Command line\n\nScanning all iRules in a directory recursively (`$PWD/tests/basic`):\n\n```shell\ndocker run --rm -v \"$PWD/tests/basic:/scandir\" simonkowallik/irulescan\n```\n\n```json\n[\n {\n \"filepath\": \"dangerous.tcl\",\n \"warning\": [\n \"Unquoted expr at `1` in `expr 1 + $one`\",\n \"Unquoted expr at `+` in `expr 1 + $one`\"\n ],\n \"dangerous\": [\"Dangerous unquoted expr at `$one` in `expr 1 + $one`\"]\n },\n {\n \"filepath\": \"ok.tcl\",\n \"warning\": [],\n \"dangerous\": []\n },\n {\n \"filepath\": \"warning.tcl\",\n \"warning\": [\n \"Unquoted expr at `1` in `expr 1 + 1`\",\n \"Unquoted expr at `+` in `expr 1 + 1`\",\n \"Unquoted expr at `1` in `expr 1 + 1`\"\n ],\n \"dangerous\": []\n }\n]\n```\n\nIf you plan to use irulescan frequently, consider adding a shell function to wrap the container execution and add it in your shell, eg. in your `.bashrc` or similar.\n\n```shell\nirulescan(){ docker run --rm -iv \"$PWD:$PWD\" -w \"$PWD\" simonkowallik/irulescan:latest \"${@:--help}\"; }\n# invoke ephemeral (--rm) container interactively (-i)\n# bind mount (-v) PWD to the same path and use it as workdir (-w)\n# pass any parameters, if none/empty, pass \"help\" (\"${@:--help}\")\n```\n\n> [!NOTE]\n> For brevity and readability the below examples use `jq` and `yq` to format the json output.\n\n```bash\nirulescan check --exclude-empty-findings ./tests/basic/ | yq -pjson -oyaml\n```\n\n```yaml\n- filepath: tests/basic/dangerous.tcl\n warning:\n - message: unsafe expression, use braces `{ .. }`\n issue_location: \"1\"\n context: expr 1 + $one\n line: 2\n - message: unsafe expression, use braces `{ .. }`\n issue_location: +\n context: expr 1 + $one\n line: 2\n dangerous:\n - message: dangerous unsafe expression, use braces `{ .. }`\n issue_location: $one\n context: expr 1 + $one\n line: 2\n- filepath: tests/basic/warning.tcl\n warning:\n - message: unsafe expression, use braces `{ .. }`\n issue_location: \"1\"\n context: expr 1 + 1\n line: 1\n - message: unsafe expression, use braces `{ .. }`\n issue_location: +\n context: expr 1 + 1\n line: 1\n - message: unsafe expression, use braces `{ .. }`\n issue_location: \"1\"\n context: expr 1 + 1\n line: 1\n dangerous: []\n```\n\n>[!NOTE]\n> Please note the differences in `\"filepath\"` between the two invocation methods.\n> This is important to consider when comparing a new scan to existing results.\n> `--exclude-empty-findings` removes the entry for the file `\"ok.tcl\"` as it has no findings.\n> `cd tests/basic; irulescan check . | jq` would have provided the same results as the docker command from the previous example.\n\nWhen specifying a file explicitly, irulescan will try to scan the file regardless of the file extension.\n\n```bash\nirulescan check --no-warn tests/basic/dangerous.tcl\n```\n\n```json\n[{\"filepath\":\"tests/basic/dangerous.tcl\",\"warning\":[],\"dangerous\":[{\"message\":\"dangerous unsafe expression, use braces `{ .. }`\",\"issue_location\":\"$one\",\"context\":\"expr 1 + $one\",\"line\":2}]}]\n```\n\n```bash\nirulescan --help\n```\n\n```bash\nirulescan is a tool to scan iRules for unexpected/unsafe expressions that may have undesirable effects like double substitution.\nhome: https://github.com/simonkowallik/irulescan\n\nUsage: irulescan \n\nCommands:\n check Scan all iRules in a directory (recursively) or the specified file or - for stdin\n checkref Scan all iRules in reference file (JSON) and compare to reference\n parsestr Parse given string or stdin\n mcpserver Run MCP server (HTTP stream transport)\n apiserver Run HTTP API server (OpenAPI v3)\n help Print this message or the help of the given subcommand(s)\n\nOptions:\n -h, --help\n Print help (see a summary with '-h')\n\n -V, --version\n Print version\n```\n\n### API Server\n\nThe irulescan container tag `:apiserver` provides a simple OpenAPI server (previously Swagger) for scanning iRule code or multiple files.\n\nStart the API server:\n\n```shell\ndocker run -t --rm -p 8000:8000 simonkowallik/irulescan:apiserver\n```\n\nScanning a single file / iRule code:\n\n```shell\ncurl -s http://localhost:8000/scan/ \\\n --data-binary '@tests/basic/dangerous.tcl' | yq -pjson -oyaml\n```\n\n```yaml\nwarning:\n - message: unsafe expression, use braces `{ .. }`\n issue_location: \"1\"\n context: expr 1 + $one\n line: 2\n - message: unsafe expression, use braces `{ .. }`\n issue_location: +\n context: expr 1 + $one\n line: 2\ndangerous:\n - message: dangerous unsafe expression, use braces `{ .. }`\n issue_location: $one\n context: expr 1 + $one\n line: 2\n```\n\nScanning multiple files:\n\n```shell\ncurl -s http://localhost:8000/scanfiles/ \\\n -F 'file=@tests/basic/warning.tcl' \\\n -F 'file=@tests/basic/ok.tcl' \\\n | yq -pjson -oyaml\n```\n\n```yaml\n- filepath: warning.tcl\n warning:\n - message: unsafe expression, use braces `{ .. }`\n issue_location: \"1\"\n context: expr 1 + 1\n line: 1\n - message: unsafe expression, use braces `{ .. }`\n issue_location: +\n context: expr 1 + 1\n line: 1\n - message: unsafe expression, use braces `{ .. }`\n issue_location: \"1\"\n context: expr 1 + 1\n line: 1\n dangerous: []\n- filepath: ok.tcl\n warning: []\n dangerous: []\n```\n\nHere is a demo of the apiserver UI:\n\n

\n\n $\"simonkowallik/irulescan:apiserver\"$ \n\n

\n\n### MCP Server\n\nStart the MCP server:\n\n```bash\ndocker run -t --rm -p 8000:8000 simonkowallik/irulescan:mcpserver\n```\n\nWith VSCode and Copilot, follow [Use MCP servers in VS Code (Preview)](https://code.visualstudio.com/docs/copilot/chat/mcp-servers#_enable-mcp-support-in-vs-code).\n\nThe below is a - per workspace - config example:\n\n```bash\nmkdir .vscode\ncat <<'EOF' > .vscode/mcp.json\n{\n \"servers\": {\n \"irulescan\": {\n \"url\": \"http://localhost:8000\"\n }\n }\n}\nEOF\n```\n\nHere is a demo of the mcpserver using VSCode:\n\n

\n\n $\"simonkowallik/irulescan:apiserver\"$ \n\n

\n\n## Additional resources\n\nFor safer authoring the VS Code iRules Extension is highly recommended:\n\n- [F5 Networks iRules by bitwisecook](https://marketplace.visualstudio.com/items?itemName=bitwisecook.iRule) [on github](https://github.com/bitwisecook/vscode-iRule)\n\n- [Avoiding Common iRules Security Pitfalls on F5 DevCentral](https://community.f5.com/t5/technical-articles/avoiding-common-irules-security-pitfalls/ta-p/306623)\n\n- [iRules Style Guide on F5 DevCentral](https://community.f5.com/t5/technical-articles/irules-style-guide/ta-p/305921)\n\n## Advanced topics\n\n### Using irulescan in CI\n\nThe container uses `irulescan` as the entry point with the default CMD set to `check .` which will scan `/scandir` recursively.\n\nWhen using a CI system with custom mount points (eg. `/custom/path`), this can be easily supported by passing a new CMD like below. Note that, like outlined above, this will change the prefix of `\"filepath\"` for each iRule file.\n\n```shell\ndocker run --rm \\\n -v \"$PWD/tests/tcl/:/custom/path\" \\\n simonkowallik/irulescan check /custom/path\n```\n\nAlso have a look at [GitHub Action: irulescan-action](https://github.com/simonkowallik/irulescan-action), which can be used when using GitHub.\n\nAlternatives are using the API Server (see below) or invoke the irulescan container as outlined above. Consider creating a scan result file to compare against known findings and known iRules. Any change in findings could then be used to fail the CI run.\n\n### Check results against a reference (previous scan result)\n\nThe `checkref` command can be used to check each file listed in that reference file. The reference file is just a saved scan. See examples below.\n\n```bash\nirulescan/ $ cd ./tests/basic\n```\n\nUsing a previous scan result (`irulescan.json`) and passing it to `checkref` via STDIN. If the check is successful, the exist code will be 0.\n\n```bash\n$ cat irulescan.json | irulescan checkref -\nOK\n\n$ echo $?\n0\n```\n\nRe-checking `irulescan_nowarn.json` with no additional options.\n\n```bash\n$ irulescan checkref irulescan_nowarn.json\nFailed reference check!\nExtra in scan_results: .[1].warning.[0].({\"message\":\"unsafe expression, use braces `{ .. }`\",\"issue_location\":\"+\",\"context\":\"expr 1 + 1\",\"line\":1})\nExtra in scan_results: .[1].warning.[1].({\"message\":\"unsafe expression, use braces `{ .. }`\",\"issue_location\":\"1\",\"context\":\"expr 1 + 1\",\"line\":1})\nExtra in scan_results: .[1].warning.[2].({\"message\":\"unsafe expression, use braces `{ .. }`\",\"issue_location\":\"1\",\"context\":\"expr 1 + 1\",\"line\":1})\nExtra in scan_results: .[2].warning.[0].({\"message\":\"unsafe expression, use braces `{ .. }`\",\"issue_location\":\"+\",\"context\":\"expr 1 + $one\",\"line\":2})\nExtra in scan_results: .[2].warning.[1].({\"message\":\"unsafe expression, use braces `{ .. }`\",\"issue_location\":\"1\",\"context\":\"expr 1 + $one\",\"line\":2})\n\n$ echo $?\n1\n```\n\nThe above example produces a failed check as the scan results produce additional findings. The exit code is 1.\n\nThe previous scan result `irulescan_nowarn.json` does not contain any warnings, using the `--no-warn` option the check succeeds.\n\n```bash\n$ irulescan checkref --no-warn irulescan_nowarn.json\nOK\n\n$ echo $?\n0\n```\n\n### CLI exit codes\n\nWhen using the `irulescan check` command:\n\n- Always exits with code `0` no matter what findings are produced\n- Errors lead to a non-zero exit code > 1 (eg. a crash)\n\nWhen using the `irulescan checkref` command:\n\n- Exits with code `0` when the reference scan matches the current results\n- Exits with code `1` when the reference scan does NOT match the current results\n- Errors lead to a non-zero exit code > 1 (eg. a crash)\n\n### Environment Variables\n\nirulescan supports several environment variables to customize its behavior across different usage modes (command line, API server, and MCP server).\n\n#### Command Line and Container\n\nFor command line and container usage, you can use `IRULESCAN_FILE_EXTENSIONS` to specify which file extensions to scan. The default value is `.tcl,.irul,.irule`. File extensions are always case insensitive. File extensions should be comma-separated without spaces. This is particularly useful when working with custom file naming conventions or when you want to scan files with non-standard extensions.\n\n```bash\nexport IRULESCAN_FILE_EXTENSIONS=\".f5rule,.f5irule,.txt\"\nirulescan check ./my-rules/\n\n# Use container with custom file extensions\ndocker run --rm -v \"$PWD:/scandir\" -e IRULESCAN_FILE_EXTENSIONS=\".f5rule,.custom\" simonkowallik/irulescan\n```\n\n#### API Server and MCP Server\n\nFor API server and MCP server modes, you can configure the listen address and logging level using `IRULESCAN_LISTEN` and `IRULESCAN_LOG` respectively.\n\nThe `IRULESCAN_LISTEN` variable defaults to `0.0.0.0:8000` and controls the address and port the server binds to. The environment variable has the highest priority and will overwrite the default listen address as well as any listen address specified as a command line option to either mcpserver or apiserver.\n\nThe `IRULESCAN_LOG` variable defaults to info and accepts standard log levels: `trace`, `debug`, `info`, `warn`, and `error`, where `trace` provides the most verbose output.\n","has_starred","hub_user","immutable_tags_settings",{"_133":11,"_134":135},"enabled","rules",[136],".*","is_automated","permissions",{"_140":17,"_141":11,"_142":11},"read","write","admin","user","storage_size",504110968,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_82":-7,"_80":-7,"_81":-7,"_25":156,"_31":32,"_159":160,"_163":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":157,"_56":57,"_58":30,"_59":60,"_61":62,"_63":64,"_65":66,"_67":45,"_68":57,"_69":54,"_70":17},[158],{"_40":41,"_31":32,"_42":43,"_44":45,"_46":47,"_48":49,"_50":43,"_51":-5,"_52":34,"_53":54,"_55":-5},"imageWithLayers",{"_40":41,"_31":32,"_42":43,"_44":45,"_46":47,"_74":161,"_48":49,"_50":43,"_51":-5,"_52":34,"_53":54,"_55":-5},[162],{"_31":77,"_52":34,"_78":79},"hasPermissionToViewRepoSettings","actionData","errors"]

simonkowallik/irulescan:apiserver-arm64