# Portfolio Developer Portfolio: Published Packages

A ruled list of maintained npm packages, each row with the name, version, license, weekly downloads, a short description, and an install command.

- Page: https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/published-packages
- Collection: [Portfolio](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro), Standard tier
- Group: [Developer Portfolio](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio)
- Created: 2026-07-04
- Preview image: https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/published-packages.png

## Install

```bash
npx shadcn@latest add @shadcn-ui-blocks/portfolio-pro-developer-portfolio-published-packages
```

Needs an API key from a Pro or Team plan: add `@shadcn-ui-blocks` to the registries in components.json with the key as an `Authorization: Bearer` header. Setup: https://www.shadcn-ui-blocks.com/docs/shadcn-cli. The MCP server installs it without the setup: https://www.shadcn-ui-blocks.com/docs/mcp.

## Depends on

- npm packages: lucide-react
- Installs to: `@/components/blocks/portfolio-pro/developer-portfolio/published-packages`

## About this block

Published Packages is a bordered list of four npm
libraries rendered as ruled rows. Each row leads with the
package name in mono, a version chip, and the license,
then a right-aligned weekly download figure beside a small
download icon. Under that sits a one line description and
a muted install command strip in mono with a copy icon.
A link to the full npm profile closes the section.

Packages is a typed array with name, version, license,
downloads, description, and install fields, so a real
registry profile drops in without touching markup. The
version chip and install strip reuse the muted chip and
code treatments, which keeps the row reading as package
metadata rather than a marketing card. The copy and
download icons are static affordances, not wired handlers.

## When to use

Reach for this block on a developer portfolio when
published libraries are a meaningful part of the record,
and a plain project list would hide the download numbers
that prove reach. The installer replaces the four package
objects with their own, keeping the description to one
honest line about what each library actually does.

A natural flow around it on a Portfolio Pro page:

**Before**

- [Open source list](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio)
- [Project repos](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio)

**After**

- [GitHub stats](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio)
- [Contact section](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/contact-sections)

## What you can display

One strong use is the maintained npm library list. Other
package layouts:

- **Single flagship.** One wide row for a headline library
  with a longer description and a usage snippet.
- **By registry.** Group rows under npm, crates.io, and
  PyPI headers for a polyglot maintainer.
- **With dependents.** Add a dependent count beside the
  downloads to signal how widely a package is relied on.

> Tip: lead with the weekly download figure only when it
> is genuinely strong; for newer packages, let the
> description and a clean install command carry the row.

## More in Portfolio Developer Portfolio

- [ADR Log](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/adr-log)
- [Api Project Card](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/api-project-card)
- [Career Timeline](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/career-timeline)
- [Code Snippet](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/code-snippet)
- [Contributions Grid](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/contributions-grid)
- [Engineering Principles](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/engineering-principles)
- [Github Stats](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/github-stats)
- [Incident Postmortem](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/incident-postmortem)
- [Now Building](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/now-building)
- [Open Source List](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/open-source-list)
- [Performance Wins](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/performance-wins)
- [Project List](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/project-list)
- [Project Repos](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/project-repos)
- [Pull Request Showcase](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/pull-request-showcase)
- [Skills and Projects](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/skills-and-projects)
- [System Design Case](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/system-design-case)
- [Tech Stack Detail](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/tech-stack-detail)
- [Terminal Intro](https://www.shadcn-ui-blocks.com/blocks/portfolio-pro/developer-portfolio/terminal-intro)
