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

@cognium/project-profile-detect

v1.1.0

Published

Detect project shape (library/application/cli/server/plugin) × environment (production/dev/sample/benchmark/test) from Maven/Gradle build files. Companion to circle-ir.

Readme

@cognium/project-profile-detect

Detect a Java project's shape (library / application / cli / server / plugin) and environment (production / dev / sample / benchmark / test) from its Maven/Gradle build files. Designed as a caller-side companion to circle-ir: the detector walks the filesystem and produces a per-file ProjectProfile map that circle-ir's analyzeOptions.projectProfile consumes.

Install

npm install @cognium/project-profile-detect circle-ir

circle-ir is a peer dependencyProjectProfile, ProjectShape, and ProjectEnv types are owned by circle-ir and re-exported from this package.

Usage

import { detectProjectProfiles } from '@cognium/project-profile-detect';
import { analyzeProject } from 'circle-ir';

const detection = await detectProjectProfiles(scanRoot, {
  // Optional: force a single profile for every file in the scan.
  forcedProfile: 'library/production',
  // Optional: glob → profile overrides (from cognium.config.json or similar).
  overrides: {
    'samples/**': 'sample/dev',
    'integration-tests/**': 'application/test',
  },
});

const result = await analyzeProject(files, {
  projectProfile: detection.profileByFile,   // Map<absolutePath, ProjectProfile>
});

DetectionResult shape:

interface DetectionResult {
  /** Per-file profile mapping (absolute paths). */
  profileByFile: Map<string, ProjectProfile>;
  /** Per-module resolution details (for explain output). */
  modules: ResolvedModule[];
  /** Files that fell back to 'unknown' (no enclosing module). */
  unknownFiles: string[];
}

Shape resolution

Precedence ladder (highest first):

  1. spring-boot plugin → server
  2. war / ear packaging → server
  3. maven-plugin / java-gradle-pluginplugin
  4. Gradle application plugin → application
  5. Source file declares public static void main(String[])application
  6. java-library plugin / module-info.java / META-INF/services/hybrid-gated: only resolves to library if the module's distribution URL is on the public-registry allowlist; otherwise falls back to application (internal helper library).
  7. Otherwise → unknown

Public-registry allowlist

Only these hosts flip the java-library signal to library (corporate Nexus / Artifactory does NOT count):

  • repo.maven.apache.org
  • repo1.maven.org
  • oss.sonatype.org
  • s01.oss.sonatype.org
  • central.sonatype.com
  • central.sonatype.org
  • plugins.gradle.org
  • jcenter.bintray.com

Environment resolution

Path-based, evaluated per file:

| Path contains | Environment | |---|---| | /test/ or /tests/ | test | | /samples/, /examples/, /demo/ | sample | | /benchmarks/, /benchmark/, /perf/ | benchmark | | /src/main/ | production | | anything else | dev |

Why caller-side?

circle-ir runs in both Node and browser environments and never reads the filesystem (Pillar I — browser/Node compatibility). Project-profile detection is the caller's responsibility; this package is the reference Node implementation.

See circle-ir/docs/ARCHITECTURE.md ADR-008 for the full decision tree and severity-transform contract.

License

MIT