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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@jupiterone/graph-cisco-secure-endpoint

v2.0.9

Published

A graph conversion tool for https://www.cisco.com/site/us/en/products/security/endpoint-security/secure-endpoint/index.html

Downloads

23

Readme

graph-cisco-secure-endpoint

Development Environment

Prerequisites

You must have Node.JS installed to run this project. If you don't already have it installed, you can can download the installer here. You can alternatively install Node.JS using a version manager like fnm or nvm.

Setup

Installing dependencies

From the root of this project, run npm install to install dependencies. If you have yarn installed, you can install dependencies by running yarn.

Loading credentials

Create a .env file at the root of this project and add environment variables to match what is in src/instanceConfigFields.json. The .env file is ignored by git, so you won't have to worry about accidentally pushing credentials.

Given this example configuration:

{
  "apiEndpoint": {
    "type": "string"
  },
  "apiClientId": {
    "type": "string"
  },
  "apiKey": {
    "type": "string",
    "mask": true
  }
}

You would provide a .env file like this:

API_ENDPOINT=<endpoint_hostname>
API_CLIENT_ID=<client-id>
API_KEY=<secret>

Valid API Endpoints for Cisco Secure Endpoint include:

  • api.amp.cisco.com
  • api.apjc.amp.cisco.com
  • api.eu.amp.cisco.com

The snake cased environment variables will automatically be converted and applied to the camel cased configuration field. So for example, CLIENT_ID will apply to the clientId config field, CLIENT_SECRET will apply to clientSecret, and MY_SUPER_SECRET_CONFIGURATION_VALUE will apply to a mySuperSecretConfigurationValue configuration field.

Running the integration

To start collecting data, run yarn start from the root of the project. This will load in your configuration and execute the steps stored in src/steps.

Project structure

This is the expected project structure for running integrations.

src/
  /instanceConfigFields.json
  /validateInvocation.ts
  /getStepStartStates.ts
  steps/
    exampleStep.ts
    // add additional steps here

Each of the files listed above contribute to creating an integration configuration.

Additional files can be placed under src and referenced from each of the integration files.

The template project hosted here provides a simple example of how an integration can be setup.

Development Docs

Please reference the @jupiterone/integration-sdk development documentation for more information on how to build integrations.