{"id":18374696,"url":"https://github.com/jupiterone/graph-signal-sciences","last_synced_at":"2025-04-06T20:30:40.533Z","repository":{"id":38787692,"uuid":"449411404","full_name":"JupiterOne/graph-signal-sciences","owner":"JupiterOne","description":"A graph conversion tool for https://www.signalsciences.com/","archived":false,"fork":false,"pushed_at":"2024-01-02T19:15:50.000Z","size":404,"stargazers_count":2,"open_issues_count":5,"forks_count":3,"subscribers_count":10,"default_branch":"main","last_synced_at":"2025-03-22T06:25:02.485Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/JupiterOne.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2022-01-18T19:01:34.000Z","updated_at":"2023-02-22T19:51:05.000Z","dependencies_parsed_at":"2023-12-05T18:46:49.307Z","dependency_job_id":"fd054184-8f56-4aac-b273-a01984d002d1","html_url":"https://github.com/JupiterOne/graph-signal-sciences","commit_stats":null,"previous_names":[],"tags_count":3,"template":false,"template_full_name":"JupiterOne-Archives/integration-template","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JupiterOne%2Fgraph-signal-sciences","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JupiterOne%2Fgraph-signal-sciences/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JupiterOne%2Fgraph-signal-sciences/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JupiterOne%2Fgraph-signal-sciences/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/JupiterOne","download_url":"https://codeload.github.com/JupiterOne/graph-signal-sciences/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247547018,"owners_count":20956471,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-06T00:15:43.479Z","updated_at":"2025-04-06T20:30:40.191Z","avatar_url":"https://github.com/JupiterOne.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# JupiterOne Integration\n\nLearn about the data ingested, benefits of this integration, and how to use it\nwith JupiterOne in the [integration documentation](docs/jupiterone.md).\n\n## Development\n\n### Prerequisites\n\n1. Install [Node.js](https://nodejs.org/) using the\n   [installer](https://nodejs.org/en/download/) or a version manager such as\n   [nvm](https://github.com/nvm-sh/nvm) or [fnm](https://github.com/Schniz/fnm).\n2. Install [`yarn`](https://yarnpkg.com/getting-started/install) or\n   [`npm`](https://github.com/npm/cli#installation) to install dependencies.\n3. Install dependencies with `yarn install`.\n4. Register an account in the system this integration targets for ingestion and\n   obtain API credentials.\n5. `cp .env.example .env` and add necessary values for runtime configuration.\n\n   When an integration executes, it needs API credentials and any other\n   configuration parameters necessary for its work (provider API credentials,\n   data ingestion parameters, etc.). The names of these parameters are defined\n   by the `IntegrationInstanceConfigFieldMap`in `src/config.ts`. When the\n   integration is executed outside the JupiterOne managed environment (local\n   development or on-prem), values for these parameters are read from Node's\n   `process.env` by converting config field names to constant case. For example,\n   `clientId` is read from `process.env.CLIENT_ID`.\n\n   The `.env` file is loaded into `process.env` before the integration code is\n   executed. This file is not required should you configure the environment\n   another way. `.gitignore` is configured to to avoid commiting the `.env`\n   file.\n\n### Running the integration\n\n1. `yarn start` to collect data\n2. `yarn graph` to show a visualization of the collected data\n3. `yarn j1-integration -h` for additional commands\n\n### Making Contributions\n\nStart by taking a look at the source code. The integration is basically a set of\nfunctions called steps, each of which ingests a collection of resources and\nrelationships. The goal is to limit each step to as few resource types as\npossible so that should the ingestion of one type of data fail, it does not\nnecessarily prevent the ingestion of other, unrelated data. That should be\nenough information to allow you to get started coding!\n\nSee the\n[SDK development documentation](https://github.com/JupiterOne/sdk/blob/main/docs/integrations/development.md)\nfor a deep dive into the mechanics of how integrations work.\n\nSee [docs/development.md](docs/development.md) for any additional details about\ndeveloping this integration.\n\n### Changelog\n\nThe history of this integration's development can be viewed at\n[CHANGELOG.md](CHANGELOG.md).\n\n### Versioning this project\n\nTo version this project and tag the repo with a new version number, run the\nfollowing (where `major.minor.patch` is the version you expect to move to):\n\n```sh\ngit checkout -b release-\u003cmajor\u003e.\u003cminor\u003e.\u003cpatch\u003e\nvim CHANGELOG.md # remember to update CHANGELOG.md with version \u0026 date!\ngit add CHANGELOG.md\nyarn version \u003cmajor\u003e.\u003cminor\u003e.\u003cpatch\u003e\ngit push --follow-tags -u origin release-\u003cmajor\u003e.\u003cminor\u003e.\u003cpatch\u003e\n```\n\n**NOTE:** It is _critical_ that the tagged commit is the _last_ commit before\nmerging to main. If any commit is added _after_ the tagged commit, the project\nwill not be published to NPM.\n\n**NOTE:** Make sure you select the _Create a merge commit_ option when merging\nthe PR for your release branch. Otherwise the publishing workflow will error\nout.\n\n**TIP:** We recommend updating your global `~/.gitconfig` with the\n`push.followTags = true` property. This will automatically add the\n`--follow-tags` flag to any new commits. See\n\u003chttps://git-scm.com/docs/git-config#Documentation/git-config.txt-pushfollowTags\u003e\n\n```\n[push]\n\tfollowTags = true\n```\n\nAfter the PR is merged to the main branch, the\n[**Build** github workflow](./.github/workflows/build.yml) should run the\n**Publish** step to publish this project to NPM.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjupiterone%2Fgraph-signal-sciences","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjupiterone%2Fgraph-signal-sciences","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjupiterone%2Fgraph-signal-sciences/lists"}