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

@yesprasad/fluent-graph

v0.2.1

Published

Dependency visibility and impact analysis for ServiceNow Fluent SDK projects

Readme

fluent-graph

Dependency visibility and impact analysis for ServiceNow Fluent SDK projects.


The Problem

You're refactoring a ServiceNow custom table. You delete a field. You deploy.

Production breaks.

14 client scripts fail. 3 business rules error out. 2 dashboards go blank.

You discover the breaking changes at runtime in production.


The Solution

fluent-graph maps every dependency in your Fluent SDK project — tables, fields, scripts, business rules, flows, catalog items — so you know what breaks before you deploy.

npx @yesprasad/fluent-graph blast incident
🔥 BLAST RADIUS ANALYSIS
Target: incident

⚠️  3 artifacts will break if you modify this table:
  • bank_incident_onload          (Client Script)
  • cs_incident_onload            (Client Script)
  • cs_incident_onchange_caller   (Client Script)

Now you know before you deploy.


Installation

Requires Node.js 18+ and an existing Fluent SDK project with @servicenow/sdk installed.

Global install:

npm install -g @yesprasad/fluent-graph

Or use without installing:

npx @yesprasad/fluent-graph analyze

Commands

Analyze — full project lineage map

fluent-graph analyze

Scans your project and prints a grouped summary of all artifacts and their relationships:

✔ Workspace SDK loaded
✔ Project loaded
✔ Graph built: 181 nodes, 141 edges

📊 LINEAGE MAP

  Client Script          9 artifacts
  Table                 10 artifacts
  Business Rule          1 artifact
  Flow Definition        1 artifact
  Catalog Item           2 artifacts
  Acl                    1 artifact
  Ui Action              1 artifact

🧠 PROJECT INSIGHTS
  Total User Artifacts: 35
  Platform Dependencies: 9
  Total Relationships:  141

Also writes fluent-graph.json to your project root for CI/CD or tooling use.


Blast — impact analysis for a specific artifact

fluent-graph blast <table_or_artifact_name>

Example:

fluent-graph blast x_1566039_seventh_customer
[FLUENT-GRAPH] BLAST RADIUS REPORT
Target: x_1566039_seventh_customer

┌────────────────────────────────┬───────────────────┬──────────────────────────────┐
│ Impacted Artifact              │ Type              │ Reason                       │
├────────────────────────────────┼───────────────────┼──────────────────────────────┤
│ x_1566039_seventh_account      │ table             │ Reference field: owner       │
│ x_1566039_seventh_call_case    │ table             │ Reference field: customer    │
│ cs_account_onchange_type       │ client_script     │ Logic attachment             │
└────────────────────────────────┴───────────────────┴──────────────────────────────┘

⚠️  PRE-DEPLOYMENT SUMMARY
  Total Impacted: 3 artifacts

CI/CD Integration

# .github/workflows/fluent-check.yml
- name: Analyze lineage
  run: npx @yesprasad/fluent-graph analyze

- name: Fail on identity conflicts
  run: |
    if grep -q '"action": "CONFLICT"' fluent-graph.json; then
      echo "❌ Identity conflicts detected"
      exit 1
    fi

Limitations

  • Tested against @servicenow/[email protected]
  • No UI visualization — output is JSON and terminal only
  • Single-project scope — does not trace cross-scope dependencies

License

MIT License — Copyright (c) 2026 Eshwar Sowbhagya Prasad Yaddanapudi


Acknowledgments

ServiceNow SDK team for building the Fluent DSL compiler MIT License

Copyright (c) 2024 ServiceNow Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Questions or issues? Open an issue on GitHub or reach out directly.

Author

Eshwar Sowbhagya Prasad Yaddanapudi

Questions or issues? Open an issue on GitHub