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

@ossy/consultancy

v1.16.3

Published

Consultancy feature package — schemas for employees, contracts, opportunities, and proposals

Downloads

6,483

Readme

@ossy/consultancy

Consultancy feature package for the Ossy platform — schemas and UI for employees, contracts, company information, vacations, and the opportunity → proposal sales pipeline.

What's included

Pages

| File | Page id | Default paths | |---|---|---| | consultancy.page.jsx | consultancy/home | /consultancy (en), /konsultverksamhet (sv) |

The home page shows company overview data (fiscal years, registration, VAT) via @ossy/calendar's useCompany hook.

Schemas (ADR 0006)

Document types are defined in *.schema.js. Import canonical ids from ConsultancySchema.

| Schema | Id | Purpose | |--------|-----|---------| | Employee | @ossy/consultancy/schema/employee | Consultant employment records | | Contract | @ossy/consultancy/schema/contract | Client contracts linked to employees | | Company Basic Info | @ossy/consultancy/schema/company-basic-info | Company registration and VAT details | | Vacation | @ossy/consultancy/schema/vacation | Employee vacation periods | | Opportunity | @ossy/consultancy/schema/opportunity | Sales pipeline leads and qualification | | Proposal | @ossy/consultancy/schema/proposal | Draft and sent proposals linked to opportunities |

Document instances are stored under /@ossy/consultancy/ (see the location export in locations.js).

Opportunity → proposal pipeline

These schemas support platform automation workflows:

  • Opportunity — tracks lead status (newqualifiedproposalwon / lost / deferred), fit scoring, contact details, and a link to a proposal via linkedProposalId.
  • Proposal — references its parent opportunity via opportunityId and progresses through draftsentaccepted / rejected.

Exports

| Export | Description | |---|---| | ConsultancySchema | Canonical schema id constants | | employeeSchema, contractSchema, … | Schema definitions for manifest build | | location | Workspace storage path (/@ossy/consultancy/) | | Definition | Feature metadata for store/sidebar (statuses: ['beta']) |

Usage

npm install @ossy/consultancy
npm run build

@ossy/app discovers pages automatically via "ossy": { "src": "./src" } in package.json. Schemas are picked up from *.schema.js files at build time.

import { ConsultancySchema, employeeSchema } from '@ossy/consultancy'

ConsultancySchema.employee
// => '@ossy/consultancy/schema/employee'

Migration from resource templates

This package migrated from *.resource.js to ADR 0006 schemas. Stored resource.type values changed:

| Before | After | |--------|-------| | @ossy/consultancy/employee | @ossy/consultancy/schema/employee | | @ossy/consultancy/contract | @ossy/consultancy/schema/contract | | @ossy/consultancy/companyBasicInfo | @ossy/consultancy/schema/company-basic-info | | @ossy/consultancy/vacation | @ossy/consultancy/schema/vacation |

Dependencies

| Package | Role | |---|---| | @ossy/schema | Canonical id grammar and schema validation | | @ossy/calendar | DataLoader, useCompany on overview page | | @ossy/design-system | Layout primitives and Page component | | @ossy/router-react | Page routing | | react | UI |