Installations
npm install @furystack/rest-client-fetchDeveloper Guide
Typescript
No
Module System
ESM
Releases
@furystack/core@10.4.6
Updated on Feb 16, 2022
@furystack/filesystem-store@2.0.30
Updated on Feb 16, 2022
@furystack/shades-nipple@1.3.16
Updated on Feb 16, 2022
@furystack/websocket-api@7.0.62
Updated on Feb 16, 2022
@furystack/shades@4.0.5
Updated on Feb 16, 2022
@furystack/rest-client-fetch@3.0.29
Updated on Feb 16, 2022
Contributors
Unable to fetch Contributors
Languages
TypeScript (99.54%)
JavaScript (0.36%)
HTML (0.05%)
CSS (0.05%)
validate.email 🚀
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Developer
furystack
Download Statistics
Total Downloads
33,818
Last Day
1
Last Week
9
Last Month
191
Last Year
5,700
GitHub Statistics
GPL-2.0 License
5 Stars
1,844 Commits
3 Watchers
4 Branches
2 Contributors
Updated on Feb 14, 2025
Maintainers
Package Meta Information
Latest Version
8.0.13
Package Id
@furystack/rest-client-fetch@8.0.13
Unpacked Size
54.77 kB
Size
14.01 kB
File Count
24
Published on
Jan 26, 2025
Total Downloads
Cumulative downloads
Total Downloads
33,818
Last Day
-50%
1
Compared to previous day
Last Week
-43.8%
9
Compared to previous week
Last Month
-57.2%
191
Compared to previous month
Last Year
-45.3%
5,700
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
2
Dev Dependencies
2
furystack
FuryStack is a flexible end-to-end framework that allows you to build complex services fast and easily.
- Written in Typescript. The public APIs are clean and readable.
- The Core is built on a top of native Node calls. Dependencies are carefully selected.
- You can create a backend in minutes with authentication, data stores, custom actions 3rd party packages. You don't have to waste your time looking for packages for entry-level functionality
- You can implement and use your own custom actions, websocket calls, data store or logger easily
- Custom front-end library with type safe JSX syntax and unidirectional data binding
- Same conceptions and design principles are shared between the frontend and the backend. DI, Logging, Disposables etc... works in the same way - and from the same package 😉
Layers of FuryStack
@furystack/core 
The entry-level logic (like store managers or server managers) and models (definition of the Physical Stores, users, roles) and some entry-level implementation (like InMemoryStore and FileStore for testing) sits here.
@furystack/repository 
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 the DI. You can subscribe to events here as well.
@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 this APIs are also handy with the @furystack/rest-client-fetch package in the browser.
Optional goodies
@furystack/auth-google 
You can log in with a Google ID Token into a FuryStack backend with this simple package.
Shades 
@furystack/shades is a UI library that helps you to create web UIs easily. The syntax is JSX and it works also with @furytechs tools like Logger or Inject. 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 a logic you'd like. 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 is a hearth and soul of the stack. In short terms - 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.
No vulnerabilities found.
Reason
13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
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
SAST tool is run on all commits
Details
- Info: SAST configuration detected: CodeQL
- Info: all commits (16) are checked with a SAST tool
Reason
5 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-x4c5-c7rf-jjgv
- Warn: Project is vulnerable to: GHSA-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
Reason
Found 0/30 approved changesets -- score normalized to 0
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
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
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
/10
Last Scanned on 2025-02-24
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