[{"_1":2,"_155":-5,"_156":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_134":135},"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.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_125":-5,"_126":11,"_127":17,"_128":11,"_129":-5,"_130":11,"_131":-5,"_132":133},"canonicalUrl","https://hub.docker.com/r/greymd/teip/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","greymd","reponame","teip","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2020-07-01T22:39:49.157435Z","description","Select partial standard input and replace with the result of another command efficiently","is_private","last_updated","2020-08-08T21:23:05.438452Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",418,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","

\n
\n \n

Highly efficient \"Masking tape\" for Shell

\n\n

\n $\"Latest$ \n \n $\"Test$ \n \n

\n\n# TL;DR\n\n

\n $\"Git$ \n

\n\n* Edit 4th and 6th columns in the CSV file\n\n```bash\n$ cat file.csv | teip -d, -f 4,6 -- sed 's/./@/g'\n```\n\n* Convert timestamps in /var/log/secure to UNIX time\n\n```bash\n$ cat /var/log/secure | teip -c 1-15 -- date -f- +%s\n```\n\n* Percent-encode bare-minimum range of the file\n\n```bash\n$ cat file | teip -og '[^-a-zA-Z0-9@:%._\\+~#=/]+' -- php -R 'echo urlencode($argn).\"\\n\";'\n```\n\n# Performance enhancement\n`teip` allows a command to focus on its own task.\n\nHere is the comparison of processing time to replace approx 761,000 IP addresses with dummy ones in 100 MiB text file.\n\n

\n $\"benchmark$ \n

\n\nSee detail on wiki > Benchmark.\n\n# Features\n\n* Allows any command to \"ignore unwanted input\" which most commands cannot do\n - The targeted command just handles selected parts of the standard input\n - Unselected parts are bypassed by `teip`\n - Flexible methods for selecting a range (Select like AWK, `cut` command, or a regular expression)\n\n* High performer\n - The targeted command's standard input/output are intercepted by multiple `teip`'s threads asynchronously.\n - If general UNIX commands on your environment can process a few hundred MB files in a few seconds, then `teip` can do the same or better performance.\n\n# Installation\n\n### On macOS (x86_64)\n\nUsing [Homebrew](https://brew.sh/)\n\n```bash\n$ brew install greymd/tools/teip\n```\n\n### With `dpkg` on Ubuntu, Debian, etc (x86_64)\n\n\n```bash\n$ wget https://git.io/teip-1.2.1.x86_64.deb\n$ sudo dpkg -i ./teip*.deb\n```\n\nSHA256: 043cf643e4757d3e41a9a85377c80e46af81baa95a32b3f1aa08ad3e69ad21ae\n\n### With `dnf` on Fedora, CentOS, RHEL, etc (x86_64)\n\n\n```bash\n$ sudo dnf install https://git.io/teip-1.2.1.x86_64.rpm\n```\n\nSHA256: 84de165b1972ea3f230c71cb3fe29365e4ec01bc904d214a2494fcf1dc652bc9\n\n### With `yum` on CentOS7, RHEL7, etc (x86_64)\n\n\n```bash\n$ sudo yum install https://git.io/teip-1.2.1.x86_64.rpm\n```\n\nSHA256: 84de165b1972ea3f230c71cb3fe29365e4ec01bc904d214a2494fcf1dc652bc9\n\n### With Docker\n\n```bash\n$ echo \"100 200 300 400\" | docker run --rm -i greymd/teip -f 3 -- sed 's/./@/g'\n```\n\n### For Windows\n\nUnfortunately, `teip` does not work on non-UNIX environment due to technical reason.\n\n### On other UNIX or other architectures (i686, ARM, etc..)\n\nPre-built binary for other architectures (i686, ARM, etc..) is not prepared for now.\nPlease build from source.\n\n### From source\n\nWith Rust's package manager cargo, you can install `teip` via:\n\n```\n$ cargo install teip\n```\n\nTo enable Oniguruma regular expression (`-G` option), build with `--features oniguruma` option.\nPlease make sure `libclang` shared library is on your environment in advance.\n\n```bash\n### Example for Ubuntu\n$ sudo apt install cargo clang\n$ cargo install teip --features oniguruma\n```\n\n```bash\n### Example for RHEL\n$ sudo dnf install cargo clang\n$ cargo install teip --features oniguruma\n```\n\n# Usage\n\n```\nUsage:\n teip -g [-oGsvz] [--] [...]\n teip -f [-d | -D ] [-svz] [--] [...]\n teip -c [-svz] [--] [...]\n teip -l [-svz] [--] [...]\n teip --help | --version\n\nOptions:\n --help Display this help and exit\n --version Show version and exit\n -g Select lines that match the regular expression \n -o -g selects only matched parts.\n -G -g adopts Oniguruma regular expressions\n -f Select only these white-space separated fields\n -d Use for field delimiter of -f\n -D Use regular expression for field delimiter of -f\n -c Select only these characters\n -l Select only these lines\n -s Execute command for each selected part\n -v Invert the sense of selecting\n -z Line delimiter is NUL instead of newline\n```\n\n## Getting Started\n\nTry this at first.\n\n```bash\n$ echo \"100 200 300 400\" | teip -f 3\n```\n\nThe result is almost the same as the input but \"300\" is highlighted and surrounded by `[...]`.\nBecause `-f 3` selects the 3rd field of space-separated input.\n\n```bash\n100 200 [300] 400\n```\n\nUnderstand that the area enclosed in `[...]` is like a hole on the masking-tape.\n\n

\n\nNext, put the `sed` and its arguments at the end.\n\n```bash\n$ echo \"100 200 300 400\" | teip -f 3 sed 's/./@/g'\n```\n\nThe result is as below.\nHighlight and `[...]` is gone then.\n\n```\n100 200 @@@ 400\n```\n\nAs you can see, the `sed` only processed the input in the \"hole\" and ignores masked parts.\nTechnically, `teip` passes only highlighted part to the `sed` and replaces it with the result of the `sed`.\n\nOff-course, any command whatever you like can be specified.\nIt is called the **targeted command** in this article.\n\nLet's try the `cut` as the targeted command to extract the first character only.\n\n```bash\n$ echo \"100 200 300 400\" | teip -f 3 cut -c 1\nteip: Invalid arguments.\n```\n\nOops? Why is it failed?\n\nThis is because the `cut` uses the `-c` option.\nThe option of the same name is also provided by `teip`, which is confusing.\n\nWhen entering a targeted command with `teip`, it is better to enter it after `--`.\nThen, `teip` interprets the arguments after `--` as the targeted command and its argument.\n\n```bash\n$ echo \"100 200 300 400\" | teip -f 3 -- cut -c 1\n100 200 3 400\n```\n\nGreat, the first character `3` is extracted from `300`!\n\nAlthough `--` is not always necessary, it is always better to be used.\nSo, `--` is used in all the examples from here.\n\nNow let's double this number with the `awk`.\nThe command looks like the following (Note that the variable to be doubled is not `$3`).\n\n```bash\n$ echo \"100 200 300 400\" | teip -f 3 -- awk '{print $1*2}'\n100 200 600 400\n```\n\nOK, the result went from 300 to 600.\n\nNow, let's change `-f 3` to `-f 3,4` and run it.\n\n```bash\n$ echo \"100 200 300 400\" | teip -f 3,4 -- awk '{print $1*2}'\n100 200 600 800\n```\n\nThe numbers in the 3rd and 4th were doubled!\n\nAs some of you may have noticed, the argument of `-f` is compatible with the __LIST__ of `cut`.\n\nLet's see how it works with `cut --help`.\n\n```bash\n$ echo \"100 200 300 400\" | teip -f -3 -- sed 's/./@/g'\n@@@ @@@ @@@ 400\n\n$ echo \"100 200 300 400\" | teip -f 2-4 -- sed 's/./@/g'\n100 @@@ @@@ @@@\n\n$ echo \"100 200 300 400\" | teip -f 1- -- sed 's/./@/g'\n@@@ @@@ @@@ @@@\n```\n\n## Select range by character\n\nThe `-c` option allows you to select a range by character-base.\nThe below example is selecting 1st, 3rd, 5th, 7th characters and apply the `sed` command to them.\n\n```bash\n$ echo ABCDEFG | teip -c 1,3,5,7\n[A]B[C]D[E]F[G]\n\n$ echo ABCDEFG | teip -c 1,3,5,7 -- sed 's/./@/'\n@B@D@F@\n```\n\nAs same as `-f`, `-c`'s argument is compatible with `cut`'s __LIST__.\n\n## Processing delimited text like CSV, TSV\n\nThe `-f` option recognizes delimited fields [like `awk`](https://www.gnu.org/software/gawk/manual/html_node/Regexp-Field-Splitting.html) by default.\n\nThe continuous white spaces (all forms of whitespace categorized by [Unicode](https://www.unicode.org/Public/UCD/latest/ucd/PropList.txt)) is interpreted as a single delimiter.\n\n```bash\n$ printf \"A B \\t\\t\\t\\ C \\t D\" | teip -f 3 -- sed s/./@@@@/\nA B @@@@ C D\n```\n\nThis behavior might be inconvenient for the processing of CSV and TSV.\n\nHowever, the `-d` option in conjunction with the `-f` can be used to specify a delimiter.\nNow you can process the CSV file like this.\n\n```bash\n$ echo \"100,200,300,400\" | teip -f 3 -d , -- sed 's/./@/g'\n100,200,@@@,400\n```\n\nIn order to process TSV, the TAB character need to be typed.\nIf you are using Bash, type `$'\\t'` which is one of [ANSI-C Quoting](https://www.gnu.org/software/bash/manual/html_node/ANSI_002dC-Quoting.html).\n\n```bash\n$ printf \"100\\t200\\t300\\t400\\n\" | teip -f 3 -d $'\\t' -- sed 's/./@/g'\n100 200 @@@ 400\n```\n\n`teip` also provides `-D` option to specify an extended regular expression as the delimiter.\nThis is useful when you want to ignore consecutive delimiters, or when there are multiple types of delimiters.\n\n```bash\n$ echo 'A,,,,,B,,,,C' | teip -f 2 -D ',+'\nA,,,,,[B],,,,C\n```\n\n```bash\n$ echo \"1970-01-02 03:04:05\" | teip -f 2-5 -D '[-: ]'\n1970-[01]-[02] [03]:[04]:05\n```\n\nThe regular expression of TAB character (`\\t`) can also be specified with the `-D` option, but `-d` has slightly better performance.\nRegarding available notations of the regular expression, refer to [regular expression of Rust](https://docs.rs/regex/1.3.7/regex/).\n\n## Matching with Regular Expression\n\nYou can also select particular lines that match a regular expression with `-g`.\n\n```bash\n$ echo -e \"ABC1\\nEFG2\\nHIJ3\" | teip -g '[GJ]\\d'\nABC1\n[EFG2]\n[HIJ3]\n```\n\nBy default, whole the line including the given pattern is selected like the `grep` command.\nWith `-o` option, only matched parts are selected.\n\n```bash\n$ echo -e \"ABC1\\nEFG2\\nHIJ3\" | teip -og '[GJ]\\d'\nABC1\nEF[G2]\nHI[J3]\n```\n\nNote that `-og` is one of the useful idiom and freuquently used in this manual.\n\nHere is an example of using `\\d` which matches numbers.\n\n```bash\n$ echo ABC100EFG200 | teip -og '\\d+'\nABC[100]EFG[200]\n\n$ echo ABC100EFG200 | teip -og '\\d+' -- sed 's/.*/@@@/g'\nABC@@@EFG@@@\n```\n\nThis feature is quite versatile and can be useful for handling the file that has no fixed form like logs, markdown, etc.\n\nHowever, you should pay attention to use it.\n\nThe below example is almost the same as above one but `\\d+` is replaced with `\\d`.\n\n```bash\n$ echo ABC100EFG200 | teip -og '\\d' -- sed 's/.*/@@@/g'\nABC@@@@@@@@@EFG@@@@@@@@@\n```\n\nAlthough the selected characters are the same, the result is different.\n\nIt is necessary to know the \"Tokenization\" of `teip` in order to understand this behavior.\n\n## Tokenization\n\n`teip` divides the standard input into tokens.\nA token that does not match the pattern will be displayed on the standard output as it is. On the other hand, the matched token is passed to the standard input of a targeted command.\nAfter that, the matched token is replaced with the result of the targeted command.\n\nIn the next example, the standard input is divided into four tokens as follows.\n\n```bash\necho ABC100EFG200 | teip -og '\\d+' -- sed 's/.*/@@@/g'\n```\n\n```\nABC => Token(1)\n100 => Token(2) -- Matched\nEFG => Token(3)\n200 => Token(4) -- Matched\n```\n\nBy default, the matched tokens are combined by line breaks and used as the new standard input for the targeted command.\nImagine that `teip` executes the following command in its process.\n\n```bash\n$ printf \"100\\n200\\n\" | sed 's/.*/@@@/g'\n@@@ # => Result of Token(2)\n@@@ # => Result of Token(4)\n```\n\n(It is not technically accurate but you can now see why `$1` is used not `$3` in one of the examples in \"Getting Started\")\n\nAfter that, matched tokens are replaced with each line of result.\n\n```\nABC => Token(1)\n@@@ => Token(2) -- Replaced\nEFG => Token(3)\n@@@ => Token(4) -- Replaced\n```\n\nFinally, all the tokens are concatenated and the following result is printed.\n\n```\nABC@@@EFG@@@\n```\n\nPractically, the above process is performed asynchronously.\nTokens being printed sequentially as they become available.\n\nBack to the story, the reason why a lot of `@` are printed in the example below is that the input is broken up into many tokens.\n\n```bash\n$ echo ABC100EFG200 | teip -og '\\d'\nABC[1][0][0]EFG[2][0][0]\n```\n\n`teip` recognizes input matched with the entire regular expression as a single token.\n`\\d` matches a single digit, and it results in many tokens.\n\n```\nABC => Token(1)\n1 => Token(2) -- Matched\n0 => Token(3) -- Matched\n0 => Token(4) -- Matched\nEFG => Token(5)\n2 => Token(6) -- Matched\n0 => Token(7) -- Matched\n0 => Token(8) -- Matched\n```\n\nTherefore, `sed` loads many newline characters.\n\n```bash\n$ printf \"1\\n0\\n0\\n2\\n0\\n0\\n\" | sed 's/.*/@@@/g'\n@@@ # => Result of Token(2)\n@@@ # => Result of Token(3)\n@@@ # => Result of Token(4)\n@@@ # => Result of Token(6)\n@@@ # => Result of Token(7)\n@@@ # => Result of Token(8)\n```\n\nThe tokens of the final form are like the following.\n\n```\nABC => Token(1)\n@@@ => Token(2) -- Replaced\n@@@ => Token(3) -- Replaced\n@@@ => Token(4) -- Replaced\nEFG => Token(5)\n@@@ => Token(6) -- Replaced\n@@@ => Token(7) -- Replaced\n@@@ => Token(8) -- Replaced\n```\n\nAnd, here is the final result.\n\n```\nABC@@@@@@@@@EFG@@@@@@@@@\n```\n\nThe concept of tokenization is also used for other options.\nFor example, if you use `-f` to specify a range of `A-B`, each field will be a separate token.\nAlso, the field delimiter is always an unmatched token.\n\n```bash\n$ echo \"AA,BB,CC\" | teip -f 2-3 -d,\nAA,[BB],[CC]\n```\n\nWith the `-c` option, adjacent characters are treated as the same token even if they are separated by `,`.\n\n```bash\n$ echo \"ABCDEFGHI\" | teip -c1,2,3,7-9\n[ABC]DEF[GHI]\n```\n\n## What command can be used?\n\nAs explained, `teip` replaces tokens on a row-by-row basis.\nTherefore, a targeted command must follow the below rule.\n\n* **A targeted command must print a single line of result for each line of input.**\n\nIn the simplest example, the `cat` command always succeeds.\nBecause the `cat` prints the same number of lines against the input.\n\n```bash\n$ echo ABCDEF | teip -og . -- cat\nABCDEF\n```\n\nIf the above rule is not satisfied, the result will be inconsistent.\nFor example, `grep` may fail.\nHere is an example.\n\n```bash\n$ echo ABCDEF | teip -og .\n[A][B][C][D][E][F]\n\n$ echo ABCDEF | teip -og . -- grep '[ABC]'\nABC\nteip: Output of given command is exhausted\n\n$ echo $?\n1\n```\n\n`teip` could not get the result corresponding to the token of D, E, and F.\nThat is why the above example fails.\n\nIf an inconsistency occurs, `teip` will exit with the error message.\nAlso, the exit status will be 1.\n\n## Advanced usage\n\n### Solid mode\n\nIf you want to use a command that does not satisfy the condition, **\"A targeted command must print a single line of result for each line of input\"**, enable \"Solid mode\" which is available with the `-s` option.\n\nSolid mode spawns the targeted command for each matched token and executes it each time.\n\n```bash\n$ echo ABCDEF | teip -s -og . -- grep '[ABC]'\n```\n\nIn the above example, understand the following commands are executed in `teip`'s procedure.\n\n```bash\n$ echo A | grep '[ABC]' # => A\n$ echo B | grep '[ABC]' # => B\n$ echo C | grep '[ABC]' # => C\n$ echo D | grep '[ABC]' # => Empty\n$ echo E | grep '[ABC]' # => Empty\n$ echo F | grep '[ABC]' # => Empty\n```\n\nThe empty result is replaced with an empty string.\nTherefore, D, E, and F tokens are replaced with empty as expected.\n\n```bash\n$ echo ABCDEF | teip -s -og . -- grep '[ABC]'\nABC\n\n$ echo $?\n0\n```\n\nHowever, this option is not suitable for processing a large file because it may significantly degrade performance instead of consolidating the results.\n\n### Overlay `teip`s\n\nAny command can be used with `teip`, surprisingly, even if it is **`teip` itself**.\n\n```bash\n$ echo \"AAA@@@@@AAA@@@@@AAA\" | teip -og '@.*@'\nAAA[@@@@@AAA@@@@@]AAA\n\n$ echo \"AAA@@@@@AAA@@@@@AAA\" | teip -og '@.*@' -- teip -og 'A+'\nAAA@@@@@[AAA]@@@@@AAA\n\n$ echo \"AAA@@@@@AAA@@@@@AAA\" | teip -og '@.*@' -- teip -og 'A+' -- tr A _\nAAA@@@@@___@@@@@AAA\n```\n\nIn other words, you can connect the multiple features of `teip` with AND conditions for more complex range selection.\nFurthermore, it works asynchronously and in multi-processes, similar to the shell pipeline.\nIt will hardly degrade performance unless the machine faces the limits of parallelism.\n\n### Oniguruma regular expression\n\nIf `-G` option is given together with `-g`, the regular expressin is interpreted as [Oniguruma regular expression](https://github.com/kkos/oniguruma/blob/master/doc/RE). For example, \"keep\" and \"look-ahead\" syntax can be used.\n\n```bash\n$ echo 'ABC123DEF456' | teip -G -og 'DEF\\K\\d+'\nABC123DEF[456]\n\n$ echo 'ABC123DEF456' | teip -G -og '\\d+(?=D)'\nABC[123]DEF456\n```\n\nThose techniques are helpful to reduce the number of \"Overlay\".\n\n### Empty token\n\nIf a blank field exists when the `-f` option is used, the blank is not ignored and treated as an empty token.\n\n```bash\n$ echo ',,,' | teip -d , -f 1-\n[],[],[],[]\n```\n\nTherefore, the following command can work (Note that `*` matches empty as well).\n\n```bash\n$ echo ',,,' | teip -f 1- -d, sed 's/.*/@@@/'\n@@@,@@@,@@@,@@@\n```\n\nIn the above example, the `sed` loads four newline characters and prints `@@@` four times.\n\n### Invert match\n\nThe `-v` option allows you to invert the selected range.\nWhen the `-f` or `-c` option is used, the complement of the selected field is selected instead.\n\n```bash\n$ echo 1 2 3 4 5 | teip -v -f 1,3,5 -- sed 's/./_/'\n1 _ 3 _ 5\n```\n\nOf course, it can also be used for the `-og` option.\n\n```bash\n$ printf 'AAA\\n123\\nBBB\\n' | teip -vr '\\d+' -- sed 's/./@/g'\n@@@\n123\n@@@\n```\n\n### NUL as line delimiter\n\nIf you want to process the data in a more flexible way, the `-z` option may be useful.\nThis option allows you to use the NUL character (the ASCII NUL character) instead of the newline character.\nIt behaves like `-z` provided by GNU sed or GNU grep, or `-0` option provided by xargs.\n\n```bash\n$ printf '111,\\n222,33\\n3\\0\\n444,55\\n5,666\\n' | teip -z -f3 -d,\n111,\n222,[33\n3]\n444,55\n5,[666]\n```\n\nWith this option, the standard input is interpreted per a NUL character rather than per a newline character.\nYou should also pay attention to that matched tokens are concatenated with the NUL character instead of a newline character in `teip`'s procedure.\n\nIn other words, if you use a targeted command that cannot handle NUL characters (and cannot print NUL-separated results), the final result can be unintended.\n\n```bash\n$ printf '111,\\n222,33\\n3\\0\\n444,55\\n5,666\\n' | teip -z -f3 -d, -- sed -z 's/.*/@@@/g'\n111,\n222,@@@\n444,55\n5,@@@\n\n$ printf '111,\\n222,33\\n3\\0\\n444,55\\n5,666\\n' | teip -z -f3 -d, -- sed 's/.*/@@@/g'\n111,\n222,@@@\n@@@\n444,55\n5,teip: Output of given command is exhausted\n```\n\nSpecifying from one line to another is a typical use case for this option.\n\n```bash\n$ cat test.html | teip -z -og '.*'\n\n\n AAA\n\n[\n

AAA

BBB

CCC

\n]\n\n\n$ cat test.html | teip -z -og '.*' -- grep -a BBB\n\n\n AAA\n\n

BBB

\n\n```\n\n# Environment variables\n\n`teip` refers to the following environment variables.\nAdd the statement to your default shell's startup file (i.e `.bashrc`, `.zshrc`) to change them as you like.\n\n### `TEIP_HIGHLIGHT`\n\n**DEFAULT VALUE:** `\\x1b[36m[\\x1b[0m\\x1b[01;31m{}\\x1b[0m\\x1b[36m]\\x1b[0m`\n\nThe default format for highlighting matched token.\nIt must include at least one `{}` as a placeholder.\n\nExample:\n```\n$ export TEIP_HIGHLIGHT=\"<<<{}>>>\"\n$ echo ABAB | teip -og A\n<<>>B<<>>B\n\n$ export TEIP_HIGHLIGHT=$'\\x1b[01;31m{}\\x1b[0m'\n$ echo ABAB | teip -og A\nABAB ### Same color as grep\n```\n\n[ANSI Escape Sequences](https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797) and [ANSI-C Quoting](https://www.gnu.org/software/bash/manual/html_node/ANSI_002dC-Quoting.html) are helpful to customize this value.\n\n# Background\n\n## Why made it?\nSee this [post](https://dev.to/greymd/teip-masking-tape-for-shell-is-what-we-needed-5e05).\n\n## Why \"teip\"?\n\n* [tee](https://en.wikipedia.org/wiki/Tee_%28command%29) + in-place.\n* Came from Irish verb \"teip\" which means \"fail\" and it can also mean \"cut off\".\n* And it sounds similar to Masking-\"tape\".\n\n# License\n\n## Modules imported from other repositories\n\nThank you so much for helpful modules!\n\n* ./src/list/ranges.rs\n - One of the module used in `cut` command of [uutils/coreutils](https://github.com/uutils/coreutils)\n - Original souce codes are distributed under MIT license\n - The license file is on the same directory\n\n## Source code\nThe scripts are available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).\n\n## Logo\n $\"Creative$
The logo of teip is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",66989903,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",722022,"full_size",30285258,"id",107059430,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:ce8df426342d35f13261b5061784c606f22ed1e2ae209f9a0812ba5a2787951f","features","","last_pulled","2026-09-21T16:49:49.731857366Z","last_pushed","2020-08-08T21:23:06Z","os","linux","os_features","os_version","size","variant","2020-08-08T21:23:05.130239Z","last_updater","last_updater_username","media_type","latest","repository",9370924,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":136,"_143":144,"_132":153,"_154":11},{"_36":137,"_38":138,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":139,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":140,"_75":11,"_76":142,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":141},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_145":60,"_146":-5,"_147":-5,"_148":149},"count","next","previous","results",[150],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":151,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[152],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

greymd/teip

Tags for greymd/teip