open-index/open-npm huggingface dataset:
npm package: @securelend/react
Description: React hooks and components for the SecureLend SDK
Latest version: 0.1.0-beta.5

# @securelend/react

React hooks and components for the SecureLend SDK.

## Installation

```bash
npm install @securelend/sdk @securelend/react
```

## Quick Start

Wrap your application with the `SecureLendProvider` and provide your API key.

```tsx
// src/App.tsx
import { SecureLendProvider } from '@securelend/react';

function App() {
  return (
    <SecureLendProvider apiKey={process.env.REACT_APP_SECURELEND_API_KEY}>
      <YourAppComponent />
    </SecureLendProvider>
  );
}
```

Then, use the custom hooks to interact with the SecureLend API.

```tsx
// src/components/LoanFinder.tsx
import { useLoanComparison, SecureLendWidget } from '@securelend/react';

function LoanFinder() {
  const { data, loading, error, widget, compare } = useLoanComparison();

  const handleCompare = () => {
    compare({
      amount: 200000,
      purpose: "equipment",
      business: {
        revenue: 1200000,
        creditScore: 720,
        timeInBusiness: 36,
      },
    });
  };

  if (loading) return <p>Loading...</p>;
  if (error) return <p>Error: {error.message}</p>;

  return (
    <div>
      <button onClick={handleCompare}>Compare Loans</button>
      {widget ? (
        <SecureLendWidget html={widget} />
      ) : (
        data?.offers.map(offer => (
          <div key={offer.offerId}>
            <h3>{offer.lender.name}</h3>
            <p>Rate: {offer.terms.interestRate.rate}%</p>
          </div>
        ))
      )}
    </div>
  );
}
```
npm package: @securelend/widgets
Description: Pre-built React UI components for the SecureLend SDK
Latest version: 0.1.0-beta.5

# @securelend/widgets

Pre-built React UI components for the SecureLend SDK.

This package provides production-ready components to quickly build user interfaces for financial product comparison.

## Installation

```bash
npm install @securelend/sdk @securelend/widgets
```

## Quick Start

Import the components and use them in your React application.

```tsx
import { LoanComparisonWidget } from '@securelend/widgets';
import { useLoanComparison } from '@securelend/react'; // Assuming you use the hooks package

function LoanFinder() {
  const { data, loading, compare } = useLoanComparison();

  // ... logic to call compare() ...

  if (loading) return <p>Loading...</p>;
  if (!data) return <p>No data yet.</p>;

  return (
    <div>
      <LoanComparisonWidget response={data} />
    </div>
  );
}
```

## Available Widgets

- `LoanComparisonWidget`
- `BankingComparisonWidget` (coming soon)
- `CreditCardComparisonWidget` (coming soon)
npm package: @securely.id/compliance-lib
Description: Secure smart contracts library for compliance in Solidity
Author: Securely
Latest version: 1.0.11

# <img src="logo.png" alt="Securely" height="40px"> Securely | contracts

**A library providing compliance checking tools for secure smart contract development.**

 * Full support of standards like [ERC20](https://docs.openzeppelin.com/contracts/erc20)
 * Reusable Solidity components to build custom contracts and complex decentralized systems.

:mage: **Not sure how to get started?** Contact us at contact@securely.id

## Security

This project is maintained by [Securely](https://securely.id) with the goal of providing a secure and reliable library of smart contract components for the ecosystem. We address security through risk management in various areas such as engineering and open source best practices, scoping and API design, multi-layered review processes, and incident response preparedness.

You are invited to report security vulnerabilities freely at contact@securely.id. Any good-faith alert will be treated with kindness.

Smart contracts are a nascent technology and carry a high level of technical risk and uncertainty. Although Securely cares very much about security, using Securely Contracts is not a substitute for a security audit.

Securely Contracts is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including Securely. As set out further in the Terms, you acknowledge that you are solely responsible for any use of Securely Contracts and you assume all risks associated with any such use.

## License

Securely Contracts is released under the [MIT License](LICENSE).
npm package: @securely.id/websdk
Description: Securely Web SDK
Author: Securely
Latest version: 1.0.9

# <img src="logo.png" alt="Securely" height="40px"> Securely Web SDK

**NPM package allowing interaction with [Securely](https://www.securely.id/)'s services.**

:mage: **Not sure how to get started?** Contact us at contact@securely.id

## Installation

```bash
npm install @securely.id/websdk
```

## License

Securely Web SDK is released under the [MIT License](LICENSE).
npm package: @secureo/eslint-config
Description: Secureo ESLint configuration
Author: Daniel Lutz
Latest version: 1.2.1

<div align="center">
    <img src="https://eslint.org/img/logo.svg" alt="ESLint Logo" height="200px">
    <h2>Secureo ESLint Configuration</h2>
</div>

# Installation

```
$ npm i --save-dev @secureo/eslint-config
```

> You must install peerDependencies yourself!

# Usage

```js
// .eslintrc
{
  "extends": "@secureo/eslint-config"
}
```
npm package: @secureo/prettier-config
Description: Secureo Prettier configuration
Author: Daniel Lutz
Latest version: 1.0.2

![Prettier Banner](https://raw.githubusercontent.com/prettier/prettier-logo/master/images/prettier-banner-light.png)

<h2 align="center">Secureo Prettier Configuration</h2>

# Installation

```
$ npm i --save-dev @secureo/prettier-config
```

# Usage

```js
// .prettierrc.js
module.exports = {
	...require("@secureo/prettier-config"),
}
```
npm package: @securerpc/msgbus
Description: Message bus that handles communication between the Dashboard and its components
Author: SEE CONTRIBUTORS
Latest version: 0.3.4

# `@securerpc/msgbus`

> `@securerpc/msgbus` manages the communication

- [@securerpc/msgbus](#--securerpc-msgbus-)
  - [Development](#development)
    - [Architecture](#architecture)
    - [Adding new message types](#adding-new-message-types)

## Development

```
npm install @securerpc/msgbus
```

```
yarn add @securerpc/msgbus
```

A new message bus can be started by instantiating a new `DashboardMessageBus`
and calling the `start()` function on it. This should almost always be done in
combination with starting a new dashboard, so you probably don't want to do this
directly. Instead you should start a new dashboard, which automatically starts
its corresponding message bus.

The `@securerpc/msgbus` does contain a bunch of exported utilities used for
connecting and communicating with the message bus that can be used directly by
other packages, although this should still only be used when developing new
packages that interface with the dashboard, rather than end-user applications.

### Architecture

The message bus works by running two separate WebSocket servers. One server is
for publishers to connect to and send requests, while the other server is for
subscribers (dashboards) to connect to and receive requests. The subscribers
respond to these requests by sending a message to the message bus with an ID
that corresponds to the request. Any requests from publishers are sent to all
subscribers, but only the first response will be returned to the publisher. When
new subscribers connect, any "unfulfilled" requests will be sent to the newly
connected subscribers as well. The message bus stays running as long as there is
at least one publisher _or_ subscriber connected. As soon as the last one
disconnects, the message bus shuts down.

### Adding new message types

Right now there are very few message types. The most important one is
`"provider"`, which sends RPC requests for the dashboard-provider. Other message
types are `"invalidate"`, which can be sent to invalidate earlier messages, and
`"log"`, which is sent by the message bus to send log messages over the wire.
The interfaces of these messages are defined inside the `@securerpc/msgbus`
package, from where they can be imported by consumers.

To add additional message types, the interface for the new message type should
be defined in this package under `lib/message/types.ts`. To use these new messge
formats, support needs to be added to any consuming packages such as
`@securerpc/dashboard` as well.

## License

MIT
npm package: @secureseco-dao/diamond-governance-sdk
Description: SDK for Diamond Governance, a ERC-2535 DAO bridge.
Author: Plopmenz
Latest version: 1.0.3

### Diamond Governace SDK
TypeScript wrapper for the Diamond Governance smart contract calls.

### Example
```
const DiamondGovernanceAddress = "< insert address of Diamond Contract >";
const [owner] = await ethers.getSigners();
const client = new DiamondGovernanceClient(DiamondGovernanceAddress, owner);
const IERC165 = await client.pure.IERC165();
console.log(await IERC165.supportsInterface("0x01ffc9a7"));
```

### Real world projects
[SecureSECO DAO webapp](https://github.com/SecureSECODAO/dao-webapp)
[Diamond Governance demo](https://github.com/Plopmenz/diamond-governance-demo)
npm package: @secureshare/nextjs
Description: SecureShare authentication SDK for Next.js applications
Author: SecureShare
Latest version: 1.0.1

# @secureshare/nextjs

Official SecureShare SDK for Next.js applications. Add complete authentication to your app in minutes.

## Installation

\`\`\`bash
npm install @secureshare/nextjs
\`\`\`

## Quick Start

### 1. Set up environment variables

Add these to your `.env.local`:

\`\`\`env
NEXT_PUBLIC_SECURESHARE_WORKSPACE_ID=your_workspace_id
NEXT_PUBLIC_SUPABASE_URL=your_supabase_url
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
\`\`\`

### 2. Wrap your app with SecureShareProvider

\`\`\`tsx
// app/layout.tsx
import { SecureShareProvider } from '@secureshare/nextjs'

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        <SecureShareProvider>
          {children}
        </SecureShareProvider>
      </body>
    </html>
  )
}
\`\`\`

### 3. Add authentication pages

\`\`\`tsx
// app/sign-in/page.tsx
import { SignIn } from '@secureshare/nextjs'

export default function SignInPage() {
  return <SignIn redirectUrl="/dashboard" />
}
\`\`\`

\`\`\`tsx
// app/sign-up/page.tsx
import { SignUp } from '@secureshare/nextjs'

export default function SignUpPage() {
  return <SignUp redirectUrl="/dashboard" />
}
\`\`\`

### 4. Protect your routes

\`\`\`tsx
// app/dashboard/page.tsx
import { protect, currentUser } from '@secureshare/nextjs/server'

export default async function DashboardPage() {
  await protect() // Redirects to /sign-in if not authenticated
  const user = await currentUser()

  return <div>Welcome, {user?.firstName}!</div>
}
\`\`\`

### 5. Use authentication in client components

\`\`\`tsx
'use client'

import { useUser, UserButton } from '@secureshare/nextjs'

export function Header() {
  const { user, isSignedIn } = useUser()

  return (
    <header>
      {isSignedIn ? (
        <UserButton />
      ) : (
        <a href="/sign-in">Sign In</a>
      )}
    </header>
  )
}
\`\`\`

## API Reference

### Client Components

- `<SecureShareProvider>` - Wrap your app to provide authentication context
- `<SignIn>` - Pre-built sign in form
- `<SignUp>` - Pre-built sign up form
- `<UserButton>` - User profile dropdown with sign out

### Client Hooks

- `useUser()` - Get current user and authentication state
- `useAuth()` - Sign in, sign up, and sign out methods
- `useOrganization()` - Get user's organization

### Server Functions

- `auth()` - Get authentication state on the server
- `currentUser()` - Get full user object on the server
- `protect()` - Protect routes (redirects if not authenticated)
- `createSecureShareClient()` - Create Supabase client for server operations

## License

MIT
npm package: @securetrading/js-payment-card
Description: JavaScript Payment card
Author: SecureTrading
Latest version: 1.0.10

**Please note a newer version of the Payment card library is available at https://gitlab.com/trustpayments-public/stjs/js-payments-card.**

**This project is no longer actively developed and only recieves dependency updates.**

<h1 align="center">Payment card</h1>

<div align="center">
  
  <!-- Build status -->  
  [![Build Status](https://travis-ci.org/SecureTrading/js-payment-card.svg?branch=master)](https://travis-ci.org/SecureTrading/js-payment-card) <!-- Test Coverage -->[![Coverage Status](https://coveralls.io/repos/github/SecureTrading/js-payment-card/badge.svg?branch=master)](https://coveralls.io/github/SecureTrading/js-payment-card?branch=master) <!-- Vulnerabilities --> [![Known Vulnerabilities](https://snyk.io/test/github/SecureTrading/js-payment-card/badge.svg?targetFile=package.json)](https://snyk.io/test/github/SecureTrading/js-payment-card?targetFile=package.json) <!-- Dependabot --> [![Dependabot badge](https://img.shields.io/badge/Dependabot-enabled-brightgreen.svg)](https://app.dependabot.com/) <!-- Browser Stack -->[![BrowserStack Status](https://automate.browserstack.com/badge.svg?badge_key=ZGFScUZkdVZ1QTNTMDFHTWRLcXV6RFd6dWdWMmFWTVJ1UjNYYVZBUy9vST0tLU11OGVqeHB5TUc0Wk9wVG9aWjNyU1E9PQ==--8911df7d51d6d8a559bec52ef47e213cdee4a18f)](https://automate.browserstack.com/public-build/ZGFScUZkdVZ1QTNTMDFHTWRLcXV6RFd6dWdWMmFWTVJ1UjNYYVZBUy9vST0tLU11OGVqeHB5TUc0Wk9wVG9aWjNyU1E9PQ==--8911df7d51d6d8a559bec52ef47e213cdee4a18f)
</div>

## Table of Contents

- [Features](#features)
- [Support](#support)

## Features
- __Animated payment card:__ Creates an animated payment card for your form
- __Card type detection:__ Performs a card lookup to detect the card type of the user as they type

## Support
Feel free to open a PR to contribute. All code is required to have 100% test coverage and to pass our unit and integration tests.

## Browser compatibility
To ensure our browser compatibility the integration tests for this project run through BrowserStack as part of the automated Travis CI pipeline. This will run the integration tests for the following supported browsers:

- Internet Explorer 9, 10 and 11
- Latest versions of the following:
  - Chrome
  - Firefox
  - Edge
  - Safari

Tested by:

<img alt="BrowserStack" src="https://raw.githubusercontent.com/SecureTrading/js-payment-card/master/browserstack-logo.png" width="300" />

## License
[MIT](https://tldrlegal.com/license/mit-license)
npm package: @securetrading/js-payments-card
Description: TypeScript Payment Card
Latest version: 1.0.23

# JS Payment Card

You can check JS Library in action by running it on your local environment. To do this, run commands below:

```
npm install
npm start
```

Then open address `https://localhost:8443` in your web browser.

## Technology Stack:

##### Tools and languages:

- [TypeScript](https://www.typescriptlang.org/)
- [ES6](https://developer.mozilla.org/en-US/docs/Web/JavaScript) + [Babel](https://babeljs.io/)
- [Webpack](https://webpack.js.org/)
- [npm](https://www.npmjs.com/)
- [Sass (SCSS + BEM)](https://sass-lang.com/)
- [PostCSS](https://postcss.org/)
- [Prettier](https://prettier.io/)
- [Stylelint](https://stylelint.io/)
- [TSLint](https://palantir.github.io/tslint/)
- [ESLint](https://eslint.org/)

##### QA:

- [Jest](https://jestjs.io/) for unit testing

## Browser compatibility:

- Internet Explorer 10 or later
- Latest versions of the following:
  - Chrome
  - Firefox
  - Edge
  - Safari

## License

- [MIT](https://opensource.org/licenses/MIT)
npm package: @securetrading/jwt-generator
Description: Generator of JSON Web Token
Author: Secure Trading
Latest version: 0.1.2
Deprecated: New version is available here: https://www.npmjs.com/package/@trustpayments/jwt-generator

# `jwtgenerator`

> Generator of JSON Web Token

## Usage
```
import { jwtgenerator } from '@securetrading/jwtgenerator';
jwtgenerator(payload, secret, iss);

or from CLI:

npm run jwtgen 'pathtofile'
```
npm package: @securetrading/ts-iin-lookup
Description: Perform an IIN lookup to determine the credit card type
Author: Secure Trading
Latest version: 0.1.2
Deprecated: New version is available here: https://www.npmjs.com/package/@trustpayments/ts-iin-lookup

# `IIN Lookup`

> Perform an IIN lookup to determine the credit card type

## Usage

```
import { iinLookup } from '@securetrading/ts-iin-lookup';
const details = iinLookup.lookup('4111111111111111');
console.log(details.type); // Payment brand e.g. VISA/MASTERCARD/AMEX etc
```
npm package: @securetrading/ts-luhn-check
Description: Validate card numbers by use of the luhncheck
Author: Secure Trading
Latest version: 0.1.2
Deprecated: New version is available here: https://www.npmjs.com/package/@trustpayments/ts-luhn-check

# `luhncheck`

> Luhn check validation for credit card payments

## Usage

```
import { luhnCheck } from '@securetrading/ts-luhn-check';
luhnCheck('4111111111111111');
```
npm package: @securingsincity/newrelic-loopback4
Description: Loopback 4 Instrumentation for Newrelic node agent
Author: prashant.bhaduria@zestmoney.in
Latest version: 1.0.1

# newrelic-loopback4
Loopback 4 Instrumentation for the [Node agent](https://github.com/newrelic/node-newrelic)

 [![Build status](https://img.shields.io/travis/zestmoney/newrelic-loopback4/master.svg?style=flat-square)](https://travis-ci.org/zestmoney/newrelic-loopback4)


### Overview

Loopback 4 uses expressjs under the hood and mounts itself as request handler. It is the default handler irrespective of the URI. So understanding the correct API URL becomes difficult. 

```
npm install newrelic-loopback4
```
```js
// index.js
require('newrelic-loopback4')
```

### Supported features

- Correct path
npm package: @securitize/easysui
Description: Easy-to-use TypeScript SDK for Sui blockchain development
Latest version: 0.1.4

# EasySui SDK

Easy-to-use TypeScript SDK for Sui blockchain development.

## Installation

```bash
npm install @easysui/sdk
# or
pnpm add @easysui/sdk
# or
yarn add @easysui/sdk
```

## Usage

```typescript
import { Config, getKeypair, deploySuiPackage } from '@easysui/sdk'

// Get configuration
const config = Config.vars

// Create keypair from private key
const keypair = getKeypair('your-private-key')

// Deploy a package
const result = await deploySuiPackage(config.PACKAGE_PATH)
```

## Features

- **Configuration Management**: Easy configuration with environment-specific settings
- **Token Utilities**: Helpers for working with Sui tokens and USDC
- **Deployment Tools**: Simplified package deployment and upgrades
- **Cost Analysis**: Gas cost estimation and analysis
- **Test Utilities**: Testing helpers for Sui development

## API Reference

### Config

```typescript
import { Config } from '@easysui/sdk'

// Access configuration variables
const vars = Config.vars

// Write configuration to .env file
Config.write(configVars)
```

### Keypair Management

```typescript
import { getKeypair } from '@easysui/sdk'

const keypair = getKeypair(privateKey)
```

### Package Deployment

```typescript
import { deploySuiPackage, upgradeSuiPackage } from '@easysui/sdk'

// Deploy new package
const deployResult = await deploySuiPackage(packagePath)

// Upgrade existing package
const upgradeResult = await upgradeSuiPackage(packagePath, upgradeCapId)
```

## Development

```bash
# Install dependencies
pnpm install

# Build the package
pnpm build

# Run tests
pnpm test

# Lint code
pnpm lint

# Format code
pnpm fix
```

## Publishing

This package uses [Changesets](https://github.com/changesets/changesets) for version management and publishing.

```bash
# Add a changeset
pnpm changeset

# Version packages
pnpm version

# Build and publish to npm
pnpm release
```

## License

MIT
npm package: @security-alert/create-issue
Description: [GitHub] Create an issue from security alert's url.
Author: azu
Latest version: 1.11.1

# @security-alert/create-issue

[GitHub] Create an issue from security alert's url.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @security-alert/create-issue --global
    # Install `security-alert-create-issue` command

Using with [npx](https://www.npmjs.com/package/npx):

    npx @security-alert/create-issue

## Usage

```
    Usage
      $ npx @security-alert/create-issue <github-security-alert-url>
 
    Inputs
      <github-security-alert-url> GitHub Security Alert URL(open|closed)
 
    Options
      --dryRun Dry-Run when it is enabled
      --token  GitHub Token, or support environment variables - GITHUB_TOKEN=xxx
      --assignees assignee user name. names are separated ,
      --labels    label name. labels are separated , 
      
    Examples
      $ GITHUB_TOKEN=xxx npx @security-alert/create-issue "https://github.com/security-alert/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/axios/open"
      $ GITHUB_TOKEN=xxx npx @security-alert/create-issue "https://github.com/security-alert/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/axios/open" --labels "security,package"
```

## Example Issue

- <https://github.com/security-alert/github-webhook-SecurityVulnerability-test/issues/8>

## Changelog

See [Releases page](https://github.com/security-alert/create-security-alert-issue/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/security-alert/create-security-alert-issue/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @security-alert/list-alerts
Description: [GitHub] listing security alert.
Author: azu
Latest version: 1.11.1

# @security-alert/list-alerts

Show list of GitHub Security Alerts.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @security-alert/list-alerts --global
    
Using with [npx](https://www.npmjs.com/package/npx):

    npx @security-alert/list-alerts

## Usage

```
    Usage
      $ npx @security-alert/list-alerts [option]
 
    Options
      --repo   Repository to get details for
               <owner>/<name>
      --token  GitHub Token, or support environment variables - GITHUB_TOKEN=xxx
      --format  json, text
  
    Examples
      $ GITHUB_TOKEN=xxx npx @security-alert/list-alerts --repo github/desktop
      $ GITHUB_TOKEN=xxx npx @security-alert/list-alerts --repo github/desktop --format json
```

## Example


```shell
$ GITHUB_TOKEN="$GITHUB_TOKEN" npx @security-alert/list-alerts --repo security-alert/github-webhook-SecurityVulnerability-test

# lodash

- PackageName: lodash
- PackageUrl: https://www.npmjs.com/package/lodash
- PackageVersion: 2.4.2
- DependenciesType: dependencies
- PackageManifestUrl: https://github.com/security-alert/github-webhook-SecurityVulnerability-test/blob/master/package-lock.json
- VulnerableVersionRange: < 4.17.5
- GitHubAlertUrl: https://github.com/security-alert/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/lodash/open


# lodash

- PackageName: lodash
- PackageUrl: https://www.npmjs.com/package/lodash
- PackageVersion: 2.4.2
- DependenciesType: dependencies
- PackageManifestUrl: https://github.com/security-alert/github-webhook-SecurityVulnerability-test/blob/master/package-lock.json
- VulnerableVersionRange: < 4.17.11
- GitHubAlertUrl: https://github.com/security-alert/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/lodash/open


# minimatch

- PackageName: minimatch
- PackageUrl: https://www.npmjs.com/package/minimatch
- PackageVersion: 3.0.0
- DependenciesType: dependencies
- PackageManifestUrl: https://github.com/security-alert/github-webhook-SecurityVulnerability-test/blob/master/package-lock.json
- VulnerableVersionRange: < 3.0.2
- GitHubAlertUrl: https://github.com/security-alert/github-webhook-SecurityVulnerability-test/network/alert/package-lock.json/minimatch/open

...(snip)...

```

## Changelog

See [Releases page](https://github.com/security-alert/create-security-alert-issue/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/security-alert/create-security-alert-issue/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @security-alert/sarif-to-issue
Description: Create an issue from SARIF file
Author: azu
Latest version: 1.11.1

# @security-alert/sarif-to-issue

Create an issue from SARIF file

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @security-alert/sarif-to-issue

## Usage

    Usage
      $ npx @security-alert/sarif-to-issue <sarif-file-path>
 
    Inputs
      <sarif-file-path> Path to sarif file path
 
    Options
      --dryRun                      Dry-Run when it is enabled
      --token                       [Required] GitHub Token, or support environment variables - GITHUB_TOKEN=xxx
      --owner                       [Required] Github repository owner for creating issue. e.g.) "azu"
      --repo                        [Required] Github repository name for creating issue. e.g.) "security-alert"
      --title                       [Required] GitHub issue title. e.g.) "Security Notice"
      --assignees                   Assignee user name of the issue. names are separated by ,(comma)
      --labels                      Label names of the issue. labels are separated by ,(comma) 
      --sarifContentOwner           [Required] GitHub Owner name of sarif content result.  e.g. "owner"
      --sarifContentRepo            [Required] GitHub Repository name of sarif content result. e.g. "repo"
      --sarifContentBranch          [Required] GitHub Repository branch name of sarif content result. e.g. "master"
      --sarifContentSourceRoot      Base path to sarif scanned source. You can set CodeQL's sourceLocationPrefix as relative value if necessary
      
    Examples
      # Create an issue to security-alert/codeql-scan-example from "./test/fixtures/xss.sarif" file
      $ GITHUB_TOKEN=xxx npx @security-alert/sarif-to-issue --title "Example Issue" --owner azu --repo codeql-scan-example --sarifContentOwner azu --sarifContentRepo codeql-scan-example --sarifContentBranch master ./test/fixtures/xss.sarif
      # Create an issue to security-alert/example-repo with "security" labels
      $ GITHUB_TOKEN=xxx npx @security-alert/sarif-to-issue output.sarif --title "Example Issue" --owner azu --repo codeql-scan-example --sarifContentOwner azu --sarifContentRepo codeql-scan-example --sarifContentBranch master ./test/fixtures/xss.sarif  --labels "security" 

## Changelog

See [Releases page](https://github.com/security-alert/security-alert/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/security-alert/security-alert/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @security-alert/share
Description: security alert shared lib
Author: azu
Latest version: 1.11.1

# @security-alert/share

Shared library for @security-alert

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @security-alert/share

## Changelog

See [Releases page](https://github.com/security-alert/create-security-alert-issue/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/security-alert/create-security-alert-issue/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @security-alliance/opencti-client
Description: TypeScript client for interacting with OpenCTI
Author: Security Alliance
Latest version: 0.5.1

# OpenCTI Client

This is a TypeScript library for interacting with OpenCTI. At the time of writing, this library supports OpenCTI version 6.7.7, but this may change.

# Local Development

## Updating the OpenCTI version

To update the autogenerated client, please clone the OpenCTI repository and check out the version that you need. Then, you can run this command.

```bash
pnpm generate $PATH_TO_OPENCTI
```

## Testing

To run the tests, please clone `OpenCTI-Platform/docker` and set the API key to `00000000-0000-0000-0000-000000000000`. After the Docker containers are up, you can run the tests with this command.

```bash
pnpm test
```

To test this package with another project, make sure the project has a `pnpm` section in the `package.json`. Then, run this command in the other project

```bash
pnpm link $PATH_TO_THIS_REPO
```

Once you're done testing, you can revert the link with this.

```bash
pnpm unlink @security-alliance/opencti-client
pnpm i
```
npm package: @security-alliance/seal-intel-sdk
Description: TypeScript client for interacting with SEAL Intel
Author: Security Alliance
Latest version: 0.2.6

# SEAL Intel SDK

## Usage

### Setup

```typescript
import { WebContentClient } from "@security-alliance/seal-intel-sdk";

// initialize the SDK with your API key
const client = new WebContentClient("https://sealisac.org", "your-api-key");
```

### Functions

```typescript
client.blockWebContent(content: WebContent, creator: Identifier<'identity'>): Promise<Indicator>;
client.unblockWebContent(content: WebContent): Promise<Indicator | undefined>;
client.trustWebContent(content: WebContent, creator: Identifier<'identity'>): Promise<Observable>;
client.untrustWebContent(content: WebContent): Promise<Observable | undefined>;
```