
Security News
The Nightmare Before Deployment
Season’s greetings from Socket, and here’s to a calm end of year: clean dependencies, boring pipelines, no surprises.
threadx
Advanced tools
threadx - Create elegant data transformation pipelines. It lets you thread values through a sequence of operations with a sense of clarity and simplicity that feels natural. And it all revolves around two key elements:
Here’s what it looks like in action:
from threadx import xf, x
xf('./data.log',
read_file,
x.splitlines(),
(map, x.strip(), x),
(map, json.loads, x),
(map, x['time'], x),
sum)
# or
xl('./data.log',
read_file,
x.splitlines(),
(map, x.strip()),
(map, json.loads),
(map, x['time']),
sum)
What’s happening here? The file content is being read, split, stripped, converted to JSON, and the execution-time summed—all in a linear and readable way. No intermediary variables, no nesting, just the data flowing from one step to the next.
The data.log file (generated by inspector) contains entries like this:
{"time": 12000, "fn": "foo", ...}
{"time": 12345, "fn": "bar", ...}
What Makes threadx Interesting?
x Factor: x acts as a placeholder for where the output of the previous step goes. It’s surprisingly flexible, supporting method calls, attribute/item lookups, and more.pip install threadx
from threadx import xf, xl, x
xf allows you to pass the result of the previous step automatically as the first argument in each new function:
xf([1, 2, 3], # => [1, 2, 3]
sum, # => 6
str) # => '6'
Or, be explicit about it:
xf([1, 2, 3],
(sum, x),
(str, x))
Want to pass the result into a different argument position? No problem:
xf(10,
(range, x, 20, 3), # same as (range, 20, 3)
list) # => [10, 13, 16, 19]
xf(20,
(range, 10, x, 3),
list) # => [10, 13, 16, 19]
xf(3,
(range, 10, 20, x),
list) # => [10, 13, 16, 19]
xl works same as xf, with just one change, that x will be passed as the last argument.
Unpacking works as usual
xf([10, 20],
(range, *x, 3), # unpack to (range, 10, 20, 3)
list) # => [10, 13, 16, 19]
data = {'a': {'b': [1, 2, 3, 4]}}
xf(data,
x['a'],
x['b'][0]) # => 1
xf(data,
x['a']['b'][:2]) # => [1, 2]
Use x.attribute_name to lookup class and instance attributes.
xf(3 + 4j,
x.real) # => 3
xf(3 + 4j,
(x.real)) # => 3
Use x.method_name() or x.method_name(args) for method calls, just like magic.
data = {'a': 1, 'b': 2}
xf(data,
x.keys(), # same as (x.keys())
list) # => ['a', 'b']
xf(data,
(x.keys()),
(list)) # => ['a', 'b']
xf(data,
x.get('c', 'Not Found')) # => 'Not Found'
Remove verbose lambdas in simple cases.
data = [[1, 2, 3, 4], [10, 20, 30, 40]]
# Normal way:
xf(data,
(map, lambda i: i[0], x),
list) # => [1, 10]
# or
xf(data,
(map, x[0], x),
list) # => [1, 10]
# or
xl(data,
(map, x[0]),
list) # => [1, 10]
# Normal way:
xf(range(12),
(filter, lambda i: i % 2 == 0, x),
list) # => [0, 2, 4, 6, 8, 10]
# or
xf(range(12),
(filter, x % 2 == 0, x),
list) # => [0, 2, 4, 6, 8, 10]
# or
xl(range(12),
(filter, x % 2 == 0),
list) # => [0, 2, 4, 6, 8, 10]
# make a tuple or list
pipeline = (read_file,
x.splitlines(),
(map, x.strip()),
(map, json.loads),
(map, x['time']),
sum)
xl('./data.log', *pipeline) # works jsut like any other function.
# Not saying to solve this problem this way,
# Just showing what `x` can do
answer_sheet = [{'a': 1, 'b': 2, 'op': op.add , 'marks': 1, 'answer': 3},
{'a': 1, 'b': 2, 'op': op.mul , 'marks': 2, 'answer': 2},
{'a': 1, 'b': 2, 'op': op.truediv, 'marks': 2, 'answer': 0.6} # <- Incorrect answer by student
]
# need 60% to pass
passing_marks = 3
# note it is not a lambda
correct_answer = x['op'](x['a'], x['b']) == x['answer']
xl(answer_sheet,
(filter, correct_answer), # <--
(map, x['marks']),
(sum),
(x >= passing_marks) # <--
) # => True
After spending a few years working with Clojure, I found myself missing its threading macros when I returned to Python (for a side project). Sure, Python has some tools for chaining operations, but nothing quite as elegant or powerful as what I was used to.
FAQs
Chaining function calls on steroids
We found that threadx demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Season’s greetings from Socket, and here’s to a calm end of year: clean dependencies, boring pipelines, no surprises.

Research
/Security News
Impostor NuGet package Tracer.Fody.NLog typosquats Tracer.Fody and its author, using homoglyph tricks, and exfiltrates Stratis wallet JSON/passwords to a Russian IP address.

Security News
Deno 2.6 introduces deno audit with a new --socket flag that plugs directly into Socket to bring supply chain security checks into the Deno CLI.