open-index/open-npm huggingface dataset:
npm package: @supranpm/supra-dapp-templates
Description: CLI to create Supra dApp templates
Author: Jatin, DevRel, Supra
Latest version: 3.4.0

## Create Supra Dapp
This package provides a starter kit for dapp developers to bootstrap easily on the Supra network. Run `npx @supranpm/supra-dapp-templates` in your terminal to get started.

### Quick Start

To create a Supra dapp, open your terminal, cd into the directory you’d like to create the dapp in, and run the following command:

```bash
npx @supranpm/supra-dapp-templates
```
Then follow the prompts!
(npx comes with npm 5.2+ and higher)

### Prerequisites
- Node and npm Installed.
- Python 3.6+

### What is supra-dapp-templates?
`npx @supranpm/supra-dapp-templates` simplifies the initial setup and configuration process, provides a modern development workflow, offers pre-made end-to-end dapp templates, and provides a range of benefits that save time and effort. Using supra-dapp-templates enables developers to build dapps quicker on Supra.

#### Templates

- **Basic Smart Contract Template:** Boilderplate Smart Contract from the docs for quick access.

- **Supra SDK Dapp Template:** Sample Supra SDK and StarKey wallet dapp for a Simple to-do list.

- **Supra Starkey Wallet Dapp Template:** Spin the Wheel dapp build on Supra MoveVM Testnet with Starkey Wallet.

- **Supra dVRF Template:** Template to get Started with Dapp on Supra dVRF using Supra MoveVM.

- **Supra Automation Template:** Template to get your first Supra Automation Task Registered for Auto Wallet Topup Usecase. 

- **Supra Push Oracles Template:** Template to integrate Supra's push oracle data feeds in Move smart contracts on Supra Move.

## Contribution
Feel free to contribute to this project by submitting pull requests or opening issues, all contributions that enhance the functionality or user experience of this project are welcome.

### How to Contribute

1. Fork the repository on GitHub.
2. Clone your forked repository to your local machine.
3. Create a new branch for your changes:

```bash
git checkout -b feature/your-feature-name
```
4. Make your changes and commit them.
5. Push your changes to your forked repository.
6. Create a pull request from your forked repository to the main repository.
npm package: @suprcrew/project-config
Description: Configure a typescript-based project with linting and testing.
Author: Marco Bunge
Latest version: 0.1.3

# Usage

Configure a typescript-based project with linting and testing.

The project expects a folder `./src` with project source files and a folder `./tests` with tests in project root.

## Configuration

Configure typescript, 

### Configure typescipt 

tsconfig.json
```json
{
  "extends": "./node_modules/@suprcrew/project-config/configs/tsconfig.base.json"
}
```

#### Usage:

```bash
./node_modules/typescript/bin/tsc
```

### Configure linting

.eslintrc.js
```js
module.exports = {
  extends: './node_modules/@jungehaie/se-config/dist/setup_se_development/eslintrc.js'
}
```
#### dev dependencies

- @typescript-eslint/eslint-plugin
- @typescript-eslint/parser
- eslint
- eslint-config-airbnb-base
- eslint-config-airbnb-typescript
- eslint-plugin-import

#### Usage

```bash
./node_modules/eslint/bin/eslint.js --color './src/**/*.ts'
```

### Configure testing framework

jest.config.js
```js
const config = require('./node_modules/@suprcrew/project-config/configs/jest.config.js');

module.exports = {
  ...config,
  "rootDir": "./"
}
```

#### Usage:

```bash
./node_modules/jest/bin/jest.js tests
```

## Extend package.json

You may configure following scripts to use them via npm script runner `npm run <name>`. 

```json
{
  "lint": "./node_modules/eslint/bin/eslint.js --color './src/**/*.ts",
  "test:run": "./node_modules/jest/bin/jest.js tests",
  "test:watch": "./node_modules/jest/bin/jest.js tests --watch",
  "test:coverage": "./node_modules/jest/bin/jest.js tests --coverage",
  "test:watch:coverage": "./node_modules/jest/bin/jest.js tests --watch --coverage",
  "test": "npm run lint; npm run test:run",
  "build": "rm -rf ./build && npm run lint && npm run test && ./node_modules/typescript/bin/tsc"
}
```

## Create project from template

Create a new project from our base template with configuration done.

### Setup

```
npm i -g create-project
```

### Install

```
npx create-project your-project-name suprcrew/project-template
```

## Change log

Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.

## Contributing

Please see [CONTRIBUTING](CONTRIBUTING.md) and [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) for details.

## Deployment

Only maintainers are allowed to deploy new versions!

1. Run `npm run release` which will update changelog, package version and creates a publishes a release and push everything to master.

## Security

If you discover any security related issues, please email marco_bunge@web.de instead of using the issue tracker.

## Credits

- [Marco Bunge][link-author]
- [All Contributors][link-contributors]

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

[link-author]: https://github.com/mbunge
[link-contributors]: https://github.com/suprcrew/project-configs/graphs/contributors
npm package: @suprdata/spec
Description: Suprdata specification provided as types and json-schema
Author: Marco Bunge
Latest version: 0.2.4

# @suprdata/spec

The SuprData specification allows the management of the entire lifecycle of specific models, the consultation of models
during several processes such as content management, ordering processes, catalog management, workflow management,
application processes and furthermore.

## Install

```bash
npm install @suprdata/spec
```

## Usage

We want to manage the players of a team.

Let's specify and model athletes and create a list of known football players.

```ts
import {model, typed} from './model';
import {Specification} from './Specification';
import {Thing} from './Thing';

const personType = typed<Specification>(('Common/Person'), {
  '@context': 'Common',
  '@version': '1',
});

const personSpec: Specification = personType({
  name: 'Player component',
  '@id': 'player/component',
});

const athleteType = typed<Thing>('SportsTeam/Athlete', {
  '@context': 'SportsTeam',
  '@baseType': 'Person',
  '@version': '1',
});

const baseAthelete = model<Thing>(athleteType({
  specification: personSpec,
  accessRights: [
    {
      name: 'public',
      '@id': 'PUBLIC'
    }
  ]
}))

const athletes: Thing[] = [
  baseAthelete({
    name: 'Harry Kane',
  }),
  baseAthelete({
    name: 'Paul Pogba',
  }),
  baseAthelete({
    name: 'Toni Kroos',
  }),
];
```

We use schemas and ajv to validate the modeled athlete and create a JSON-Response for our API.

```ts
import {thingSchema} from './schemas';

const validAthletes = athletes.filter((athlete) => {
  const validateAthlete = ajv(thingSchema);
  const valid = validate(athlete)
  if (!valid) console.log(validate.errors)
});

emitResponse(JSON.stringify(validAthletes));
```

Supr data spec helps to create consistent data and helps to exchange between different systems, eg. between an API and Website.

## Change log

Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.

## Contributing

Please see [CONTRIBUTING](CONTRIBUTING.md) and [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) for details.

## Deployment

Only maintainers are allowed to deploy new versions!

1. Run `npm run release` which will update changelog, package version and creates a publishes a release and push
   everything to master.

## Security

If you discover any security related issues, please email marco_bunge@web.de instead of using the issue tracker.

## Credits

- [Marco Bunge][link-author]
- [All Contributors][link-contributors]

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

[link-author]: https://github.com/mbunge
[link-contributors]: https://github.com/suprdata/spec/graphs/contributors
npm package: @supreeth_tp/git-mcp-server
Description: MCP server that summarizes daily git activity and posts worklogs to JIRA
Author: Supreeth TP
Latest version: 1.0.17

# git-mcp-server

MCP server that summarizes daily git activity and generates human-readable worklogs.

Note: the automatic JIRA posting was removed — this project now focuses on producing
clear, human-readable daily summaries from git history. You can publish the produced
worklog text to JIRA or any other system yourself, or re-add an integration as needed.

Quick start

1. Copy `.env.example` to `.env` and adjust any environment variables you want (for example `SINCE` or `DRY_RUN`).
2. Install deps: `npm install` or run `npm run install-deps`.
3. Start the server (default uses stdio MCP transport): `npm start`.

Example (dry-run):

```
DRY_RUN=1 node mcp-server.js
```

From your MCP client call the `worklog/write` tool with a `ticketId` argument.

Package name and publishing

This repository has been prepared for publishing under a scoped package name that you control to avoid npm ownership conflicts:

- Package name: `@supreeth_tp/git-mcp-server`

You can either publish the package from your account or distribute the generated tarball.

Publish from your account (recommended):

```
# Ensure you're logged in as the correct npm user
npm whoami

# Publish scoped package as public
npm publish --access public
```

Install from a tarball (if you prefer to share the built file):

```
# from the repo root (example tarball name)
npm install ./supreeth_tp-git-mcp-server-1.0.16.tgz
```

Notes and customization

- The `cli/generate-worklog.js` script can produce the same dry-run summary without running the MCP transport; point it at a repo with `--repo` or set `GIT_WORK_TREE`.
- The time window used for collection is controlled by the `SINCE` environment variable (default: `1 day ago`).
- The summarizer lives in `lib/summarize.js` and formats commits and file changes into a human-readable bullet list.

If you want the server to automatically post to JIRA again, I can add a pluggable integration that sends the text to JIRA, Slack, or other APIs behind a config flag.
npm package: @supremeboy18/learnstorybook-design-system
Description: Learn Storybook design system):Storybook design systems tutorial
Author: Nur Islam
Latest version: 0.2.0

# Storybook design system tutorial

The Storybook design system tutorial is a subset of the full [Storybook design system](https://github.com/storybookjs/design-system/), created as a learning resource for those interested in learning how to write and publish a design system using best in practice techniques.

Learn more in [Storybook tutorials](https://storybook.js.org/tutorials/).
npm package: @supremespiders/ui-lib
Description: Angular 20 + PrimeNG standalone UI components
Latest version: 0.2.6

# @primengscraperbase/ui-lib

A comprehensive UI component library built with Angular 20 and PrimeNG, featuring reusable components for modern web applications.

## Features

- 🚀 Built with Angular 20 and PrimeNG 20
- 🎨 Modern, responsive UI components
- 🔧 TypeScript support with full type definitions
- 📱 Mobile-first design approach
- 🎯 Easy to integrate and customize
- 🧪 Well-tested components

## Installation

```bash
npm install @primengscraperbase/ui-lib
```

## Peer Dependencies

This library requires the following peer dependencies:

```json
{
  "@angular/common": "^20.1.3",
  "@angular/core": "^20.1.3",
  "primeng": "^20.0.1"
}
```

## Available Components

### Core Components
- **BaseComponent** - Base component with common functionality
- **SampleComponent** - Sample component for demonstration
- **LogsComponent** - Logging and monitoring component
- **UsersComponent** - User management component
- **TasksComponent** - Task management component
- **InputComponent** - Input handling component
- **ScraperComponent** - Web scraping component

### Admin Components
- **AdminLogsComponent** - Administrative logging component
- **ChangePasswordComponent** - Password change functionality

### Shared Components
- **ConfirmationComponent** - Confirmation dialogs
- **ToastComponent** - Toast notifications
- **SimpleLoginComponent** - Simple login form

## Usage

### Import the library

```typescript
import { UiLibModule } from '@primengscraperbase/ui-lib';

@NgModule({
  imports: [
    UiLibModule,
    // ... other imports
  ],
  // ... rest of module config
})
export class AppModule { }
```

### Use components in templates

```html
<app-sample></app-sample>
<app-logs></app-logs>
<app-users></app-users>
```

## Development

### Building the library

```bash
# Development build
npm run build:lib

# Production build
npm run build:lib:prod
```

### Testing

```bash
npm test
```

## Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

## Support

For support and questions:
- Create an issue on GitHub
- Check the documentation
- Review the examples

## Version History

- **0.0.1** - Initial release with core components

## Changelog

### 0.0.1
- Initial release
- Core component library
- Angular 20 and PrimeNG 20 support
- TypeScript definitions
- Responsive design components
npm package: @supremum/remark-bibtex
Description: Remark plugin to generate citations from a bibtex file
Author: dfeng
Latest version: 0.2.7

# Custom Changes

 - Use `[@Wasserman1994]` notation instead of `(@Wasserman1994)`
 - Use citation key as footnote identifier
 - Add `(Wasserman & Faust, 1994)[^Wasserman1994]` instead of just `[^1]` (in case of numeric references being used/created elsewhere)
 - Use Harvard bibliography format

# remark-bibtex

Remark-bibtex is a [remark](https://github.com/wooorm/remark) plugin to generate footnoted citations from a `bibtex` file. It uses [`citation-js`](https://github.com/citation-js/citation-js) to load a specified `.bib` file from which citations will be retrieved and added to the markdown file's footnotes section.

Citation keys take the form of `(@citationKey)`: where "citationKey" corresponds to a bibtex entry in the provided `.bib` file. The citation key will be replaced with a numbered footnote reference corresponding to the bibliography entry in footnotes section.

In order to work, this package has to be chained to the [`remark-footnotes`](https://github.com/remarkjs/remark-footnotes) package, which adds the necessary markdown footnoting capability.

```md
# My Document

So here is my citation (@Wasserman1994). End of story.
```

Will become:

```md
So here is my citation[^1]. End of story.

[^1]: 1\. Wasserman S, Faust K. Social Network Analysis. Cambridge: Cambridge University Press; 1994.
```

## Install

```sh
yarn add remark-footnotes @benchmark-urbanism/remark-bibtex
```

## Usage

```js
const remark = require('remark')
const footnotes = require('remark-footnotes')
const remarkBibtex = require('@benchmark-urbanism/remark-bibtex')

const bibtexFilePath = './example/example.bib'

remark()
  .use(footnotes)
  .use(remarkBibtex, { bibtexFile: bibtexFilePath })
  .process('Ref A: (@Harris2020) Ref B: (@Wasserman1994)')
  .then((content) => content.toString())
  .then((markdown) => console.log(markdown))
  .catch((err) => console.error(err))
```

Will give:

```md
Ref A:[^1] Ref B:[^2]

[^1]: 1\. Harris CR, Millman KJ, van der Walt SJ, Gommers R, Virtanen P, Cournapeau D, et al. Array programming with NumPy. Nature \[Internet]. 2020 Sep;585(7825):357–62. Available from: http://www.nature.com/articles/s41586-020-2649-2
[^2]: 2\. Wasserman S, Faust K. Social Network Analysis. Cambridge: Cambridge University Press; 1994.
```

### Options

### options.bibtexFile

A mandatory filepath to the `.bib` file to be loaded by `citation-js`

## License

MIT © Gareth Simons
npm package: @supriyadies-work/na-design-system
Description: Design System package for Nisa Aulia Portfolio
Latest version: 1.3.8

# @supriyadies-work/na-design-system

Design system package for **Nisa Aulia Portfolio** — design tokens, React components, and theme scales (nisaaulia / supriyadies).

**Documentation & visual reference:** [nisaaulia.com/design-pattern](https://nisaaulia.com/design-pattern)

We’re open to feedback and improvements. Suggestions, issues, and pull requests are welcome.

---

## Installation

```bash
npm install @supriyadies-work/na-design-system
# or
yarn add @supriyadies-work/na-design-system
```

### Peer dependencies

Ensure these are installed in your project:

- `react` ^18.0.0
- `react-dom` ^18.0.0
- `next` ^14.0.0 (if using Next.js)
- `next-themes` ^0.4.0 (for theming)
- `lottie-react` ^2.4.0 (for Lottie animations)

---

## Usage

### Components

```tsx
import { Button, Card, ScaleProvider } from "@supriyadies-work/na-design-system";

// Default scale: nisaaulia
<ScaleProvider>
  <Button>Primary</Button>
  <Card>...</Card>
</ScaleProvider>

// Scale: supriyadies
<ScaleProvider defaultScale="supriyadies">
  <App />
</ScaleProvider>
```

Per-component imports (better tree-shaking):

```tsx
import { Button } from "@supriyadies-work/na-design-system/components/Button";
```

### Tokens (JS)

```tsx
import { tokens, getToken, getCSSVar, theme } from "@supriyadies-work/na-design-system";
// or
import { tokens } from "@supriyadies-work/na-design-system/js/tokens";
```

### Tokens (CSS)

In your global CSS or layout:

```css
@import "@supriyadies-work/na-design-system/css";
```

For scale-specific variables (per brand):

```css
@import "@supriyadies-work/na-design-system/css/scale";
```

### Utilities

```tsx
import { cn, useScale, getScaleConfig } from "@supriyadies-work/na-design-system";
```

---

## Package exports

| Export | Description |
|--------|-------------|
| `.` | All components, tokens, utils, and scale |
| `./components` | Component index |
| `./components/*` | Single component (e.g. `Button`, `Card`) |
| `./tokens` | Token object (JS) |
| `./js/tokens` | Same, alternate path |
| `./css` | CSS variables (`tokens.css`) |
| `./css/scale` | Scale CSS (nisaaulia / supriyadies) |
| `./utils` | `cn`, validation, etc. |
| `./docs` | Documentation metadata (JSON) |

---

## Scales (brands)

Two theme scales are supported:

- **nisaaulia** — default
- **supriyadies**

Use `ScaleProvider` and `defaultScale` to choose a scale; components and tokens follow the active scale.

---

## Development scripts

```bash
npm run build          # Full build (tokens + compile + assets + docs)
npm run build:watch    # Watch tokens
npm run build:tokens   # Style Dictionary only
npm run build:docs     # Generate docs metadata
```

---

## References

- **Design patterns & docs:** [nisaaulia.com/design-pattern](https://nisaaulia.com/design-pattern)
- **Repository:** [github.com/supriyadies-work/na-design-system](https://github.com/supriyadies-work/na-design-system)