Gathering detailed insights and metrics for @furystack/rest-service
Gathering detailed insights and metrics for @furystack/rest-service
Installations
npm install @furystack/rest-serviceDeveloper Guide
BETA
Typescript
No
Module System
ESM
Releases
287
@furystack/core@10.4.6
@furystack/core@10.4.6
Updated on Feb 16, 2022
@furystack/filesystem-store@2.0.30
@furystack/filesystem-store@2.0.30
Updated on Feb 16, 2022
@furystack/shades-nipple@1.3.16
@furystack/shades-nipple@1.3.16
Updated on Feb 16, 2022
@furystack/websocket-api@7.0.62
@furystack/websocket-api@7.0.62
Updated on Feb 16, 2022
@furystack/shades@4.0.5
@furystack/shades@4.0.5
Updated on Feb 16, 2022
@furystack/rest-client-fetch@3.0.29
@furystack/rest-client-fetch@3.0.29
Updated on Feb 16, 2022
Languages
4
TypeScript
JavaScript
HTML
CSS
TypeScript (99.57%)
JavaScript (0.33%)
HTML (0.05%)
CSS (0.05%)
Developer
furystack
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
GPL-2.0 License
5 Stars
1,887 Commits
2 Watchers
5 Branches
2 Contributors
Updated on Jun 25, 2025
Maintainers
1
Package Meta Information
Latest Version
10.0.24
Package Id
@furystack/rest-service@10.0.24
Unpacked Size
647.27 kB
Size
116.11 kB
File Count
346
Published on
Jun 25, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
furystack
FuryStack is a flexible, end-to-end framework that allows you to build complex services quickly and easily.
- Written in TypeScript. The public APIs are clean and readable.
- The core is built on top of native Node.js calls. Dependencies are carefully selected.
- You can create a backend in minutes with authentication, data stores, custom actions, and 3rd-party packages. You don't have to waste time searching for packages for entry-level functionality.
- You can implement and use your own custom actions, WebSocket calls, data stores, or loggers easily.
- Custom front-end library with type-safe JSX syntax and unidirectional data binding.
- The same concepts and design principles are shared between the frontend and backend. DI, logging, disposables, etc. work in the same way—and from the same package. 😉
Layers of FuryStack
@furystack/core 
The entry-level logic (like store managers or server managers), models (definitions of physical stores, users, roles), and some entry-level implementations (like InMemoryStore and FileStore for testing) are included here.
@furystack/repository 
A repository is a collection of DataSets. A DataSet is like an extended version of a physical store—you can use a context (like a UserContext) for authorization or entity manipulation from DI. You can also subscribe to events here.
@furystack/rest 
If you want to communicate with the world, this package will be your friend. You can define your API as a TypeScript interface and implement it on the backend with @furystack/rest-service. Consuming these APIs is also easy with the @furystack/rest-client-fetch package in the browser.
Optional Goodies
@furystack/auth-google 
You can log in with a Google ID Token to a FuryStack backend with this simple package.
Shades 
@furystack/shades is a UI library that helps you create web UIs easily. The syntax is JSX and it also works with FuryStack tools like Logger or Inject. It uses unidirectional data binding.
Utility Packages
@furystack/utils 
A collection of useful tools like Disposables with using() and usingAsync() helpers, deepMerge, Tracer, and an ultra-lightweight Observer/Observable implementation.
@furystack/logging 
A powerful logging library that allows you to create log entries with scopes, levels, and custom data, and process them with your own logic. You can collect telemetry or create a crash dump collector.
@furystack/inject 
Inject is a DI/IoC utility that allows you to handle your dependencies easily and is the heart and soul of the stack. In short—just mark your services as Injectable() and use injector.getInstance(...) to retrieve them.
An injector can be extended with extension methods, so you can configure your whole app in one place in a type-safe way.
Other Packages
@furystack/cache
Simple in-memory caching utility to improve performance and reduce redundant computations.
@furystack/filesystem-store
Filesystem-based store implementation, ideal for lightweight or experimental use.
@furystack/i18n
General internationalization and translation management for FuryStack applications.
@furystack/mongodb-store
MongoDB physical store implementation for scalable, document-based storage.
@furystack/redis-store
Redis physical store implementation for fast, in-memory data storage (note: some features like filter() and count() are not supported).
@furystack/security
Password management, authentication, and authorization utilities.
@furystack/sequelize-store
Sequelize-based store implementation for SQL databases.
@furystack/shades-i18n
Internationalization support for the Shades UI library.
@furystack/shades-mfe
Micro frontend management utilities for Shades.
@furystack/shades-showcase-app
Minimal showcase application demonstrating FuryStack Shades features.
@furystack/websocket-api
WebSocket implementation for real-time communication in FuryStack.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: GNU General Public License v2.0: LICENSE:0
Reason
no binaries found in the repo
Reason
SAST tool is run on all commits
Details
- Info: SAST configuration detected: CodeQL
- Info: all commits (16) are checked with a SAST tool
Reason
0 existing vulnerabilities detected
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'actions' permission set to 'read': .github/workflows/codeql-analysis.yml:28
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/codeql-analysis.yml:29
- Warn: no topLevel permission defined: .github/workflows/build-test.yml:1
- Warn: no topLevel permission defined: .github/workflows/check-version-bump.yml:1
- Warn: no topLevel permission defined: .github/workflows/codeql-analysis.yml:1
- Warn: no topLevel permission defined: .github/workflows/npm-release.yml:1
- Warn: no topLevel permission defined: .github/workflows/showcase-ui-tests.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/build-test.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/build-test.yml/develop?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test.yml:37: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/build-test.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/check-version-bump.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/check-version-bump.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/check-version-bump.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/check-version-bump.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/codeql-analysis.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/codeql-analysis.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/codeql-analysis.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:71: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/codeql-analysis.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npm-release.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/npm-release.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/npm-release.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/npm-release.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/showcase-ui-tests.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/showcase-ui-tests.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/showcase-ui-tests.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/showcase-ui-tests.yml/develop?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/showcase-ui-tests.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/furystack/furystack/showcase-ui-tests.yml/develop?enable=pin
- Info: 0 out of 13 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Score
5.5
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More