npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@logkat/broker-parser

v0.1.0

Published

A robust, standalone TypeScript library for parsing transaction CSV exports from various stock brokers.

Readme

Broker Parser

A robust, standalone TypeScript library for parsing transaction CSV exports from various stock brokers. This library normalizes transaction data into a common format, handling currency conversions, transaction types, and ISIN extraction.

Features

  • Multi-Broker Support: Automatically detects and parses CSVs from supported brokers.
  • Normalization: Unifies transaction types (BUY, SELL, DIVIDEND, etc.) across brokers.
  • Currency Handling: Extracts account currency, native currency, and exchange rates.
  • ISIN Extraction: Reliably finds ISIN codes for accurate instrument identification.
  • Export Support: Convert parsed transactions into formats like Yahoo Finance CSV.
  • CLI Support: Command-line interface for bulk processing and exporting without writing code.
  • Data Enrichment: Helper utilities to resolve Tickers (e.g. from ISIN) before export.
  • Type Safe: Written in TypeScript with full type definitions.

Supported Brokers

  • Avanza (Sweden)
  • Nordnet (Sweden/Nordics)
  • (More can be added by implementing the BrokerParser interface)

Installation

Library Usage

To install from GitHub Packages, you need to configure your .npmrc file:

echo "@logkat:registry=https://npm.pkg.github.com" >> .npmrc

Then install the package:

npm install @logkat/broker-parser
# or
pnpm add @logkat/broker-parser

CLI Usage

The library provides a powerful CLI for bulk processing and ticker resolution.

# Basic export (defaults to Yahoo resolution)
broker-parser export input.csv -o output.csv

# Specific resolvers (stacked in order)
broker-parser export input.csv --ticker-file custom.json --yahoo

# Control over resolution strategies
broker-parser export input.csv --yahoo-isin --yahoo-name

| Flag | Description | | ---------------- | -------------------------------------------------------- | | --yahoo | Use both ISIN and Name search (Default: true) | | --yahoo-isin | Trigger only ISIN-based search | | --yahoo-name | Trigger only Name-based search (fuzzy matching) | | --ticker-file | Use a local JSON/CSV mapping file (priority) | | --no-yahoo | Disable all automatic lookups | | --cache <path> | Path to resolution cache (Default: .ticker-cache.json) |

Usage

Library Usage (TypeScript)

Parsing transactions

import { parseTransaction } from '@logkat/broker-parser';

const transaction = parseTransaction(row);

Advanced Ticker Resolution

The library and CLI support "stacked" resolvers. You can prioritize local data and then fall back to various cloud providers.

Ticker Mapping Formats

When using --ticker-file or FileTickerResolver, you can use JSON or CSV files.

JSON Format (Object or Array):

// Simple object (Key can be ISIN or Security Name)
{
  "US0378331005": "AAPL",
  "Meta Platforms A": "META"
}

// Or an array of objects
[
  { "isin": "US0378331005", "ticker": "AAPL" },
  { "name": "Microsoft", "ticker": "MSFT" }
]

CSV Format:

isin,name,ticker
US0378331005,,AAPL
,Microsoft,MSFT

Library Example

import {
  enrichTransactions,
  YahooISINResolver,
  YahooNameResolver,
  FileTickerResolver,
  LocalFileTickerCache,
} from '@logkat/broker-parser';

const enriched = await enrichTransactions(transactions, {
  resolvers: [
    new FileTickerResolver('./manual-mapping.json'),
    new YahooISINResolver(),
    new YahooNameResolver(),
  ],
  cache: new LocalFileTickerCache('./cache.json'),
});

Auto-Detecting Broker Format

The library automatically detects the format based on unique headers (e.g., "Typ av transaktion" for Avanza vs "Transaktionstyp" for Nordnet). You can also force a format:

// Force Avanza parser
const txn = parseTransaction(row, 'Avanza');

Identifying Accounts

If you are parsing a large CSV with multiple accounts, you can extract unique account identifiers:

import { identifyAccounts } from '@logkat/broker-parser';

const accounts = identifyAccounts(allRows);
// Returns: [{ id: '12345', name: 'My ISK', count: 50 }, ...]

Exporting Data

You can export normalized transactions to various formats (e.g., for importing into other tools).

import { YahooFinanceExporter } from '@logkat/broker-parser';

// Convert transactions to Yahoo Finance CSV
const result = YahooFinanceExporter.export(parsedTransactions);
console.log(result.content); // CSV string

Enriching Data (Tickers)

Brokers outputs (Avanza/Nordnet) often lack the actual Ticker Symbol required by Yahoo Finance (they provide ISIN or Name instead). To fix this, you can use enrichTransactions with a resolver.

import {
  enrichTransactions,
  YahooFinanceExporter,
} from '@logkat/broker-parser';

// 1. Define or use a built-in resolver
const myResolver = {
  name: 'My Custom Resolver',
  resolve: async (isin: string, name: string) => {
    if (isin === 'US0378331005') return { ticker: 'AAPL' };
    return { ticker: null };
  },
};

// 2. Enrich
const enriched = await enrichTransactions(parsedTransactions, {
  resolvers: [myResolver],
});

// 3. Export
const csv = YahooFinanceExporter.export(enriched);

Custom Caching

The library provides a TickerCache interface. You can implement your own (e.g., using Redis or a Database) to persist resolutions.

interface TickerCache {
  get(key: string): Promise<TickerResolution | undefined>;
  set(key: string, value: TickerResolution): Promise<void>;
}

API Reference

parseTransaction(row: Record<string, string>, format?: BrokerFormat): ParsedTransaction | null

Parses a raw CSV row into a normalized transaction object. Returns null if the row cannot be parsed.

identifyAccounts(data: Record<string, string>[]): AccountSummary[]

Scans a dataset to find all unique account IDs present in the file.

ParsedTransaction Interface

  • date: Date object
  • type: 'BUY' | 'SELL' | 'DIVIDEND' | 'DEPOSIT' | 'WITHDRAW' | 'INTEREST' | 'TAX' | 'OTHER'
  • name: string (Security name, e.g. "Apple Inc")
  • ticker: string (Ticker symbol, e.g. "AAPL")
  • quantity: number
  • price: number
  • total: number
  • currency: string (Account Currency)
  • nativeCurrency: string (Asset Currency)
  • isin: string (optional)
  • ...and more.

Migration Guide

If you are moving from an internal implementation to this library:

  1. Replace Imports: Change your imports from your local file:

    - import { parseTransaction } from '@/lib/parser';
    + import { parseTransaction } from '@logkat/broker-parser';
  2. Check Config: Ensure your project handles the ParsedTransaction return type correctly, as some deprecated fields might have been cleaned up.

  3. Dependencies: This library has zero runtime dependencies (except standard JS/TS features).

Coding Guidelines

This project follows strict naming conventions for financial terminology. See CODING_GUIDELINES.md for details.

Key terminology:

  • ticker: Stock ticker symbol (e.g., "AAPL", "META")
  • name: Company/security name (e.g., "Apple Inc")
  • symbol: DEPRECATED - do not use; treat as ticker if encountered in external APIs

Adding a New Broker

We welcome contributions! To add support for a new broker:

  1. Create a Parser File: Create a new file (e.g., src/parsers/mybroker.ts) implementing the BrokerParser interface.

    import { BrokerParser } from './types';
    import { parseNumber, normalizeType } from './utils';
    
    export const MyBrokerParser: BrokerParser = {
      name: 'MyBroker',
      canParse: (row) => !!(row['UniqueHeader'] && row['AnotherHeader']),
      parse: (row) => {
        // ... parsing logic mapping to ParsedTransaction
        return {
          date: new Date(row['Date']),
          type: normalizeType(row['Type']),
          // ...
        };
      },
    };
  2. Register the Parser: Import and add your parser to src/index.ts in the getParsers() function and update the parseTransaction logic if needed.

  3. Add Tests: Add a test case in tests/parser_brokers.test.ts with a sample transaction row to verify it parses correctly.

Development & Testing

  1. Install Dependencies:

    pnpm install
  2. Run Quality Checks:

    # Format code
    pnpm format
    
    # Check formatting
    pnpm format:check
    
    # Type check
    pnpm type-check
    
    # Lint
    pnpm lint
  3. Run Tests:

    # Run tests in watch mode
    pnpm test
    
    # Run tests with coverage
    pnpm test:coverage
  4. Build:

    pnpm build
  5. Run All Checks (same as CI):

    pnpm format:check && pnpm type-check && pnpm lint && pnpm build && pnpm test:coverage

License

MIT