Libraries

Scriptling provides 90+ libraries organized by capability. Availability depends on the binary, execution mode, and host registration; it is not safe to assume every library is present.

Know the import name? Jump to the A–Z list of every library.

Python-Style Libraries

Modules that mirror Python’s standard library, grouped by subject:

• Data Formats: json, yaml, toml, msgpack, bytes
• Text Processing: re, string, html, html.parser, difflib, shlex, textwrap, io
• Math & Numbers: math, random, statistics, base64, hashlib, hmac, uuid, secrets
• Collections & Iteration: collections, itertools, functools, contextlib
• Time & System: time, datetime, platform, sys, logging
• File System: os, os.path, pathlib, glob, fs, shutil, tempfile, tarfile, zipfile
• HTTP & Process: requests, scriptling.oauth, urllib.parse, subprocess

The standard set (json, re, time, datetime, math, random, statistics, base64, hashlib, hmac, uuid, string, html, textwrap, difflib, io, platform, urllib.parse, collections, itertools, functools, contextlib, msgpack) has no access to the host and is registered together by stdlib.RegisterAll. The rest are extended libraries, registered one by one because they reach the file system, network, processes or host: see Availability.

Scriptling Libraries

The scriptling.* libraries provide functionality beyond Python’s standard library:

• AI: LLM clients, agents, memory, tool schemas
• Databases: SQLite, SQL, Valkey, BadgerDB, and the ORM
• MCP: MCP clients and tool authoring
• Messaging: Telegram, Discord, Slack, console
• Networking: Gossip, multicast, unicast, DNS, WebSocket
• Packages: Read files and metadata from loaded app/plugin bundles
• Plugins: Control library for executable plugins
• Provisioning: File and fetch provisioning
• Runtime: Background tasks, HTTP, JSON-RPC, MCP, KV, sync, sandbox
• Templates: Go-powered HTML and text templates
• Utilities: Console, containers, Nomad, grep, find, CSV, XML, secrets, and more

All Libraries A–Z

Every library by the name you import it as. Use the cheat sheet for quick examples of the common ones.

Availability

A bare scriptling.New() environment has no libraries; embedders register every capability they intend to expose. The default CLI setup composes a broader set, subject to execution mode and disable flags.

There is no universal extended-library RegisterAll. stdlib.RegisterAll covers only the standard libraries; CLI composition and plugin discovery are separate from the embedding API. See Library Registration for individual calls.

Security and Capability Boundaries

Registration grants scripts the host process’s authority for that surface. In particular:

• filesystem, subprocess, environment, secret, and provisioning libraries can read, write, execute, or disclose host data according to their configured restrictions;
• the outbound libraries (requests, scriptling.oauth, wait_for, WebSocket, unicast, multicast, gossip, Nomad, AI, MCP, provision.fetch, the Slack, Discord and Telegram libraries, and container endpoints a script supplies) obey an embedding netsecurity.Config or the CLI network-policy file when one is passed at registration, but HTTP clients the embedding application builds itself and plugin processes are separate surfaces and do not inherit it;
• container and Nomad libraries can control available local runtimes or remote cluster workloads;
• runtime HTTP/JSON-RPC/MCP/plugin servers and messaging handlers create remotely reachable entry points; authentication and authorization remain the application’s responsibility;
• plugin loading and package bundles add host-selected code and content, while provisioning can change files or fetch remote content.

Register only what a script needs, apply each library’s own controls, and use OS/container egress and process isolation where a library has no matching in-process policy. See the Security Guide and each library’s security section for details.

Getting Help

Use the help() function within scripts:

import json
help(json)