Package idxfile implements encoding and decoding of packfile idx files.
Package objfile implements encoding and decoding of object files.
Package gomarklint provides a fast Markdown linter for checking common formatting issues in Markdown files, including heading structure, blank lines, duplicate headings, and link validation.
Package i18n is a simple language manager, use INI format file.
Package threemf writes 3MF (3D Manufacturing Format) files from triangle meshes produced by github.com/soypat/gsdf.
unified-ir-reader reads and decodes __.PKGDEF files from Go .a archives and prints their contents in human-readable format.
Package s2prot is a decoder/parser of Blizzard's StarCraft II replay file format (*.SC2Replay).
Package binarycookies implements a decoder for the Binary Cookies file format used by Safari and other WebKit-based applications on macOS and iOS.
Package aw is a "plug-and-play" workflow development library/framework for Alfred 3 & 4 (https://www.alfredapp.com/). It requires Go 1.13 or later. It provides everything you need to create a polished and blazing-fast Alfred frontend for your project. As of AwGo 0.26, all applicable features of Alfred 4.1 are supported. The main features are: AwGo is an opinionated framework that expects to be used in a certain way in order to eliminate boilerplate. It *will* panic if not run in a valid, minimally Alfred-like environment. At a minimum the following environment variables should be set to meaningful values: NOTE: AwGo is currently in development. The API *will* change and should not be considered stable until v1.0. Until then, be sure to pin a version using go modules or similar. Be sure to also check out the _examples/ subdirectory, which contains some simple, but complete, workflows that demonstrate the features of AwGo and useful workflow idioms. Typically, you'd call your program's main entry point via Workflow.Run(). This way, the library will rescue any panic, log the stack trace and show an error message to the user in Alfred. In the Script box (Language = "/bin/bash"): To generate results for Alfred to show in a Script Filter, use the feedback API of Workflow: You can set workflow variables (via feedback) with Workflow.Var, Item.Var and Modifier.Var. See Workflow.SendFeedback for more documentation. Alfred requires a different JSON format if you wish to set workflow variables. Use the ArgVars (named for its equivalent element in Alfred) struct to generate output from Run Script actions. Be sure to set TextErrors to true to prevent Workflow from generating Alfred JSON if it catches a panic: See ArgVars for more information. New() creates a *Workflow using the default values and workflow settings read from environment variables set by Alfred. You can change defaults by passing one or more Options to New(). If you do not want to use Alfred's environment variables, or they aren't set (i.e. you're not running the code in Alfred), use NewFromEnv() with a custom Env implementation. A Workflow can be re-configured later using its Configure() method. See the documentation for Option for more information on configuring a Workflow. AwGo can check for and install new versions of your workflow. Subpackage update provides an implementation of the Updater interface and sources to load updates from GitHub or Gitea releases, or from the URL of an Alfred `metadata.json` file. See subpackage update and _examples/update. AwGo can filter Script Filter feedback using a Sublime Text-like fuzzy matching algorithm. Workflow.Filter() sorts feedback Items against the provided query, removing those that do not match. See _examples/fuzzy for a basic demonstration, and _examples/bookmarks for a demonstration of implementing fuzzy.Sortable on your own structs and customising the fuzzy sort settings. Fuzzy matching is done by package https://godoc.org/go.deanishe.net/fuzzy AwGo automatically configures the default log package to write to STDERR (Alfred's debugger) and a log file in the workflow's cache directory. The log file is necessary because background processes aren't connected to Alfred, so their output is only visible in the log. It is rotated when it exceeds 1 MiB in size. One previous log is kept. AwGo detects when Alfred's debugger is open (Workflow.Debug() returns true) and in this case prepends filename:linenumber: to log messages. The Config struct (which is included in Workflow as Workflow.Config) provides an interface to the workflow's settings from the Workflow Environment Variables panel (see https://www.alfredapp.com/help/workflows/advanced/variables/#environment). Alfred exports these settings as environment variables, and you can read them ad-hoc with the Config.Get*() methods, and save values back to Alfred/info.plist with Config.Set(). Using Config.To() and Config.From(), you can "bind" your own structs to the settings in Alfred: See the documentation for Config.To and Config.From for more information, and _examples/settings for a demo workflow based on the API. The Alfred struct provides methods for the rest of Alfred's AppleScript API. Amongst other things, you can use it to tell Alfred to open, to search for a query, to browse/action files & directories, or to run External Triggers. See documentation of the Alfred struct for more information. AwGo provides a basic, but useful, API for loading and saving data. In addition to reading/writing bytes and marshalling/unmarshalling to/from JSON, the API can auto-refresh expired cache data. See Cache and Session for the API documentation. Workflow has three caches tied to different directories: These all share (almost) the same API. The difference is in when the data go away. Data saved with Session are deleted after the user closes Alfred or starts using a different workflow. The Cache directory is in a system cache directory, so may be deleted by the system or "system maintenance" tools. The Data directory lives with Alfred's application data and would not normally be deleted. Subpackage util provides several functions for running script files and snippets of AppleScript/JavaScript code. See util for documentation and examples. AwGo offers a simple API to start/stop background processes via Workflow's RunInBackground(), IsRunning() and Kill() methods. This is useful for running checks for updates and other jobs that hit the network or take a significant amount of time to complete, allowing you to keep your Script Filters extremely responsive. See _examples/update and _examples/workflows for demonstrations of this API.
Package aw is a "plug-and-play" workflow development library/framework for Alfred 3 & 4 (https://www.alfredapp.com/). It requires Go 1.13 or later. It provides everything you need to create a polished and blazing-fast Alfred frontend for your project. As of AwGo 0.26, all applicable features of Alfred 4.1 are supported. The main features are: AwGo is an opinionated framework that expects to be used in a certain way in order to eliminate boilerplate. It *will* panic if not run in a valid, minimally Alfred-like environment. At a minimum the following environment variables should be set to meaningful values: NOTE: AwGo is currently in development. The API *will* change and should not be considered stable until v1.0. Until then, be sure to pin a version using go modules or similar. Be sure to also check out the _examples/ subdirectory, which contains some simple, but complete, workflows that demonstrate the features of AwGo and useful workflow idioms. Typically, you'd call your program's main entry point via Workflow.Run(). This way, the library will rescue any panic, log the stack trace and show an error message to the user in Alfred. In the Script box (Language = "/bin/bash"): To generate results for Alfred to show in a Script Filter, use the feedback API of Workflow: You can set workflow variables (via feedback) with Workflow.Var, Item.Var and Modifier.Var. See Workflow.SendFeedback for more documentation. Alfred requires a different JSON format if you wish to set workflow variables. Use the ArgVars (named for its equivalent element in Alfred) struct to generate output from Run Script actions. Be sure to set TextErrors to true to prevent Workflow from generating Alfred JSON if it catches a panic: See ArgVars for more information. New() creates a *Workflow using the default values and workflow settings read from environment variables set by Alfred. You can change defaults by passing one or more Options to New(). If you do not want to use Alfred's environment variables, or they aren't set (i.e. you're not running the code in Alfred), use NewFromEnv() with a custom Env implementation. A Workflow can be re-configured later using its Configure() method. See the documentation for Option for more information on configuring a Workflow. AwGo can check for and install new versions of your workflow. Subpackage update provides an implementation of the Updater interface and sources to load updates from GitHub or Gitea releases, or from the URL of an Alfred `metadata.json` file. See subpackage update and _examples/update. AwGo can filter Script Filter feedback using a Sublime Text-like fuzzy matching algorithm. Workflow.Filter() sorts feedback Items against the provided query, removing those that do not match. See _examples/fuzzy for a basic demonstration, and _examples/bookmarks for a demonstration of implementing fuzzy.Sortable on your own structs and customising the fuzzy sort settings. Fuzzy matching is done by package https://godoc.org/go.deanishe.net/fuzzy AwGo automatically configures the default log package to write to STDERR (Alfred's debugger) and a log file in the workflow's cache directory. The log file is necessary because background processes aren't connected to Alfred, so their output is only visible in the log. It is rotated when it exceeds 1 MiB in size. One previous log is kept. AwGo detects when Alfred's debugger is open (Workflow.Debug() returns true) and in this case prepends filename:linenumber: to log messages. The Config struct (which is included in Workflow as Workflow.Config) provides an interface to the workflow's settings from the Workflow Environment Variables panel (see https://www.alfredapp.com/help/workflows/advanced/variables/#environment). Alfred exports these settings as environment variables, and you can read them ad-hoc with the Config.Get*() methods, and save values back to Alfred/info.plist with Config.Set(). Using Config.To() and Config.From(), you can "bind" your own structs to the settings in Alfred: See the documentation for Config.To and Config.From for more information, and _examples/settings for a demo workflow based on the API. The Alfred struct provides methods for the rest of Alfred's AppleScript API. Amongst other things, you can use it to tell Alfred to open, to search for a query, to browse/action files & directories, or to run External Triggers. See documentation of the Alfred struct for more information. AwGo provides a basic, but useful, API for loading and saving data. In addition to reading/writing bytes and marshalling/unmarshalling to/from JSON, the API can auto-refresh expired cache data. See Cache and Session for the API documentation. Workflow has three caches tied to different directories: These all share (almost) the same API. The difference is in when the data go away. Data saved with Session are deleted after the user closes Alfred or starts using a different workflow. The Cache directory is in a system cache directory, so may be deleted by the system or "system maintenance" tools. The Data directory lives with Alfred's application data and would not normally be deleted. Subpackage util provides several functions for running script files and snippets of AppleScript/JavaScript code. See util for documentation and examples. AwGo offers a simple API to start/stop background processes via Workflow's RunInBackground(), IsRunning() and Kill() methods. This is useful for running checks for updates and other jobs that hit the network or take a significant amount of time to complete, allowing you to keep your Script Filters extremely responsive. See _examples/update and _examples/workflows for demonstrations of this API.
Package i18n is a simple language manager, use INI format file.
Package fits implements a pure-Go reader/writer for the FITS (Flexible Image Transport System) file format as defined by the FITS Standard v4.0.
Package gomarklint provides a fast Markdown linter for checking common formatting issues in Markdown files, including heading structure, blank lines, duplicate headings, and link validation.
Package openmcdf provides a Go implementation of the Compound File Format (also known as OLE Compound Document), which is the binary file format used by Microsoft Office applications (Word, Excel, PowerPoint) and other software that uses OLE (Object Linking and Embedding) technology.
Package goreadstat provides reading and writing support for SAS, SPSS, and Stata statistical data files. It uses the ReadStat C library via cgo for high-performance native file format support. Read and write: Read only: Reading a file: Writing a file: Read operations support various options: Write operations also support options:
Package ocrline provides Marshal and Unmarshal functions for fixed-width line-based file formats such as Nets AvtaleGiro, OCR Giro, and Bankgirot AutoGiro.
Package ocrline provides Marshal and Unmarshal functions for fixed-width line-based file formats such as Nets AvtaleGiro, OCR Giro, and Bankgirot AutoGiro.
Package packager implements a cloud-native encrypted archive format using an "Indexed-Tail" layout optimised for O(1) random-access retrieval over byte-range-capable storage (local files, S3, GCS, …).
Package ical implements the iCalendar file format.
Package awssecuritylakeexporter exports OCSF-formatted logs as Parquet files to AWS Security Lake via S3.
Package xls provides support for reading and writing Microsoft Excel 97-2003 binary format (.xls) files, also known as BIFF8 (Binary Interchange File Format).
Package rdb implements parsing and encoding of the Redis RDB file format.
Package s2prot is a decoder/parser of Blizzard's StarCraft II replay file format (*.SC2Replay).
Package s2prot is a decoder/parser of Blizzard's StarCraft II replay file format (*.SC2Replay).
Package applog configures slog for gitea.auvem.com/go-toolkit/app.Lifecycle with optional JSON file output and tint console formatting.
Package csv reads and writes comma-separated values (CSV) files. There are many kinds of CSV files; this package supports the format described in RFC 4180, except that Writer uses LF instead of CRLF as newline character by default. A csv file contains zero or more records of one or more fields per record. Each record is separated by the newline character. The final record may optionally be followed by a newline character. White space is considered part of a field. Carriage returns before newline characters are silently removed. Blank lines are ignored. A line with only whitespace characters (excluding the ending newline character) is not considered a blank line. Fields which start and stop with the quote character " are called quoted-fields. The beginning and ending quote are not part of the field. The source: results in the fields Within a quoted-field a quote character followed by a second quote character is considered a single quote. results in Newlines and commas may be included in a quoted-field results in
Package aasx provides functionality for reading and writing packaged file format of an Asset Administration Shell (AAS) v3.
binformat.go — pure binary format helpers for .evtx file construction.
Package hdf5 provides a pure Go implementation for reading HDF5 files. It supports HDF5 format versions 0, 2, and 3, with capabilities for reading datasets, groups, attributes, and various data layouts.
Package egmanifest parses Epic Games manifest files in both binary and JSON formats.
Package vortex provides a native Go implementation of the Vortex columnar file format.
Package blob provides a file archive format optimized for random access via HTTP range requests against OCI registries.
Package goalembic provides a pure Go implementation of the Alembic file format for reading and writing animated 3D scene data.
Package bisign implements Bohemia Interactive signature and key file formats used by Arma and DayZ (.biprivatekey, .bikey, .bisign).
Package pile provides a compact single-file world provider for dragonfly built on the pile v2 format.
Package conf is a library to read conf format files.
Package vdf provides a comprehensive parser and writer for Valve's VDF (Valve Data Format) files.
Package txtar implements a trivial text-based file archive format.
Package hl7 provides a parser for HL7 version 2.x messages. The parser reads HL7v2 messages encoded in the ER7 (pipe-delimited) format and returns a structured representation. It has zero external dependencies, requires Go 1.23+, and is safe for concurrent use after parsing. HL7v2 messages have a hierarchical structure: Delimiter characters are extracted from each message's MSH segment header and are not assumed to be the standard set (|^~\&), although that is typical. ParseMessage copies the input, extracts delimiters from the MSH header, merges any ADD continuation segments into their preceding segments per HL7v2.5.1 Section 2.5.2, and splits the message into segments by \r. This is the only phase that allocates. All deeper access — fields, repetitions, components, and subcomponents — is performed by scanning the segment's raw bytes on each call. No parsed results are cached; the sub-message types (Field, Repetition, Component, Subcomponent) are lightweight value types holding only a []byte slice and a Delimiters struct. Escape processing is deferred until String() is called. A consumer that reads only MSH-9 (message type) never pays the cost of scanning OBX observation segments. Get retrieves values using terser-style location strings and returns a Value. ParseLocation parses the string into a Location struct, and Location.String implements the inverse. Get returns a zero Value when the location is invalid or the value is not present — consistent with how Field(n), Rep(n), and Component(n) return zero values for out-of-range indices rather than errors. Field values in non-UTF-8 charsets (e.g. Latin-1 / ISO 8859-1 declared in MSH-18) can be decoded with DecodeString. A ValueMapper is a func([]byte) ([]byte, error) that converts post-unescape bytes to UTF-8. DecodeString is available on Value, Field, Repetition, Component, and Subcomponent: When decode is nil, DecodeString behaves identically to String() with no extra allocation. Unescape always runs before the mapper. The \C..\ and \M..\ charset escape sequences are passed through verbatim by Unescape; a sophisticated ValueMapper may parse them, but a simple byte-level mapper will treat them as-is. Segments returns a []Segment slice. Filter by type with seg.Type(): Navigate the hierarchy using Field, Rep, Component, and SubComponent: Index conventions: Field is 0-based (0 = segment type, 1+ = fields). Rep is 0-based. Component and SubComponent are 1-based. Out-of-range access returns zero values, enabling chained access without nil checks. Count methods are available at each level: FieldCount, RepetitionCount, ComponentCount, and SubComponentCount. Reader modes: ModeAuto (default, detects framing), ModeMLLP (strict MLLP), ModeRaw (MSH-boundary detection). ReadMessage returns one parsed message at a time; EachMessage iterates until EOF. Without WithMLLP, messages are written as raw bytes with a trailing \r. With WithMLLP, messages are wrapped in 0x0B...0x1C 0x0D framing. Transform applies changes to a message and returns a new Message, leaving the original unmodified: Field-level change constructors: Replace sets a value, Null sets the HL7 null (""), Omit clears a field, Move copies src to dst then clears src, Copy copies src to dst while preserving the source, MapValue applies a ValueMapper to a single location, and MapAllValues applies a ValueMapper to every leaf in the message (except MSH-1 and MSH-2). The mapper receives unescaped bytes; its output is re-escaped before storage. Segment-level change constructors add, remove, or reorder entire segments: DeleteSegment and DeleteAllSegments are no-ops when the target is absent; both return ErrCannotDeleteMSH if given "MSH". InsertSegmentAfter and InsertSegmentBefore return ErrSegmentNotFound when the reference segment is absent. Segment-level and field-level changes compose freely in one call. TransformWith additionally re-encodes all delimiters to a new set: MessageBuilder constructs messages from scratch: Use WithDelimiters to override the default delimiter set. SetNull sets a field to the HL7 null value. The builder is reusable after Build — subsequent Set calls modify its state. Ack creates an acknowledgment message in response to a parsed message: AckCode constants: AA, AE, AR (application level), CA, CE, CR (commit level). Options: WithText sets MSA-3 for error context, WithTimestamp overrides the default time.Now for MSH-7, and WithErrors adds ERR segments from validation issues. The ACK copies delimiters and swaps sender/receiver fields from the original MSH. WithErrors accepts a slice of Issue (from Validate) and produces one ERR segment per issue with error location (ERR-2), severity (ERR-4), application error code (ERR-5), and diagnostic information (ERR-7): Validate checks a parsed message against a user-provided Schema: Schema has four optional maps (Messages, Segments, DataTypes, Tables) plus a Checks slice for message-level custom validators. Only populated maps trigger validation. Schema types support JSON/YAML/TOML struct tags. Validation runs in three phases: structure (segment presence, order, cardinality via MessageDef), content (field presence, length, format, table values via SegmentDef/DataTypeDef/TableDef, plus FieldCheckFunc and SegmentCheckFunc validators), and custom checks (MessageCheckFunc from schema.Checks for cross-segment business rules). Concatenate reassembles multi-page query responses. When a server splits a large response across several messages using DSC (Continuation) segments, call Concatenate to merge them in order: Concatenate strips the trailing DSC segment from the receiver and the leading MSH segment from the argument, then returns a new Message containing the remaining segments. The DSC-1 continuation pointer is not interpreted; the caller is responsible for retrieving subsequent pages. ParseBatch parses a BHS/BTS-wrapped group of messages: ParseFile parses an FHS/FTS-wrapped file containing batches: Both are tolerant: header and trailer segments are optional. Escape replaces delimiter characters in data with HL7 escape sequences. Unescape resolves escape sequences back to literal values. Both have a zero-allocation fast path when no escaping is needed. Escape processing is deferred — Unescape runs only when String() is called, not during parsing. Bytes() returns raw data without escape processing. Per the HL7 specification, there is a distinction between empty and null fields: Use IsNull() and IsEmpty() to distinguish these cases; HasValue() returns true when neither empty nor null. All four hierarchy types (Field, Repetition, Component, Subcomponent) as well as Value share these methods. Parse-time errors use sentinel errors (ErrMessageTooShort, ErrNoMSHSegment, ErrInvalidDelimiter, etc.) that can be checked with errors.Is. ParseError wraps a sentinel with position and context for detailed diagnostics. Access-time methods (Field, Rep, Component, SubComponent) return zero values for out-of-range indices rather than errors, enabling ergonomic chained access. Validate never returns an error — it returns a *ValidationResult containing a Valid bool and a slice of Issue structs with Severity, Location, Code, and Description. See the examples/ directory for runnable programs demonstrating end-to-end workflows including stream reading, validation, transformation, and writing.
Package cookiemonster provides methods for parsing Netscape format cookie files into slices of http.Cookie
Package tiled is to to parse Tiled map editor file format (TMX).