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

@oprt/icons-c2

v0.1.0

Published

OPERATOR operational icons (comms, status, tracks, sensors, platforms, command) as React components and consistent SVG assets.

Readme

@oprt/icons-c2

79 icons for operational concepts: comms and datalinks, asset status, threats and tracks, mission readiness, sensor and ISR modes, platforms, geospatial readouts, time and tempo, electronic warfare and cyber, classification, and command and reporting. 76 are recommended and 3 are kept for existing imports.

import { SecureComms } from "@oprt/icons-c2";

<SecureComms size={16} /> Link secured
<Emcon size={24} title="EMCON active" />

Icons are decorative by default. Name an icon-only button on the button itself; use title, aria-label, or aria-labelledby when an icon independently conveys meaning. Every component forwards its ref to the SVG and accepts normal SVG props alongside size, color, title, and weight="regular". The shared wrapper comes from @oprt/icons, so all three icon packages share one optical stroke, accessibility behavior, and drawing contract: a 24-unit grid, a one-unit stroke at 24px (1.5 units at 16px), flat caps, miter joins, and currentColor paint.

Scope

These are UI chrome for tables, panels, filters, legends, and feeds. They never render tactical map symbology, including the Platform / Entity glyphs on a common operating picture: use a MIL-STD-2525 symbology engine for affiliation frames and echelon modifiers. Keep a visible label for ambiguous actions, operational states, and sensor disciplines.

Grid also exists in @oprt/icons. Alias the C2 one where you import it: import { Grid as CoordinateGrid } from "@oprt/icons-c2". Range shadows a platform global (the DOM Range), so alias it too. Radio shares a name with the @oprt/react Radio control; import the icon as RadioIcon when using both: import { Radio as RadioIcon } from "@oprt/icons-c2".

Radio identifies a handheld radio. Radar identifies a radar scan view or function; RadarSystem identifies physical radar equipment with a panel array. Satellite and Satcom share the selected diagonal body with wide, divided solar arrays; Satcom adds communication arcs. Pair equipment and functions with visible labels.

Three exports are outside the recommended set and keep working: NewContact and IffInterrogate are retired (use visible status text or a labeled action), and Uav is deprecated in favor of FixedWing, which it renders.

Tree-shaking

The package is sideEffects: false, and every icon is a pure top-level declaration, so a bundler keeps only the icons you import. A test bundles one icon and fails if another one is kept.

Raw SVG assets

The package ships 24px assets at @oprt/icons-c2/svg/<kebab-name>.svg and 16px assets at @oprt/icons-c2/svg/16/<kebab-name>.svg, for example:

@oprt/icons-c2/svg/secure-comms.svg
@oprt/icons-c2/svg/16/secure-comms.svg

The complete set includes 158 SVGs: every export in both sizes. Use the dedicated 16px file at 16px; resizing the 24px file does not select the stronger stroke.

Assets are decorative, like the components: aria-hidden="true", no <title>. An inlined asset that conveys meaning needs its own name, so add one where you inline it:

<svg role="img" aria-label="Secure comms" …><path … /></svg>

Remove aria-hidden when you add role="img" and a name. Inline SVG inherits the text color; <img> does not. Give a meaningful <img> alt text and a decorative one an empty alt.

Run pnpm --filter @oprt/icons-c2 build to regenerate both sizes. The test suite renders every component and requires the files to match exactly, with none missing, stale, or extra. pnpm --filter @oprt/icons-c2 verify:svg runs the same check against the built package.