Gathering detailed insights and metrics for @octokit-next/request
Gathering detailed insights and metrics for @octokit-next/request
Gathering detailed insights and metrics for @octokit-next/request
Gathering detailed insights and metrics for @octokit-next/request
@octokit/plugin-request-log
Log all requests and request errors
@octokit/request
Send parameterized requests to GitHub's APIs with sensible defaults in browsers and Node
@octokit/request-error
Error class for Octokit request errors
@octokit/endpoint
Turns REST API endpoints into generic request options
npm install @octokit-next/request
79.7
Supply Chain
98.8
Quality
79.2
Maintenance
100
Vulnerability
99.6
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
22 Stars
274 Commits
3 Forks
8 Watching
3 Branches
14 Contributors
Updated on 26 Nov 2024
JavaScript (79.5%)
TypeScript (20.5%)
Cumulative downloads
Total Downloads
Last day
-44.8%
128
Compared to previous day
Last week
72.6%
2,849
Compared to previous week
Last month
14.8%
7,190
Compared to previous month
Last year
-33.9%
96,106
Compared to previous year
1
Experimental Octokit SDK for exploration only - DO NOT USE 🚫⚠️
We use this repository to implement new features without the legacy of the current Octokit
implementation.
This project is built as a monorepo using npm workspaces and is publishing native ES Modules. To set it up and run the tests Node 18 is required.
Currently working on:
⚠️ This is an experimental SDK not meant for actual usage.
1import { Octokit } from "octokit-next"; 2 3const octokit = new Octokit(); 4 5const { data } = await octokit.request("GET /repos/{owner}/{repo}", { 6 owner: "octokit", 7 repo: "octokit-next.js", 8}); 9 10console.log(data);
A list of breaking changes compared to latest @octokit/*
modules
Node 16 and other JavaScript runtime environments that lack a global fetch()
method are no longer supported out-of-the-box. A fetch
method such as provided by the node-fetch
npm module can be passed to make Octokit work in these environments.
For @octokit-next/core
and other SDKs built upon it you can do this
1import { Octokit } from "octokit-next"; 2import fetch from "node-fetch"; 3 4const octokit = new Octokit({ request: { fetch } });
For the static @octokit-next/request
method you can do this
1import { request } from "@octokit-next/request"; 2import fetch from "node-fetch"; 3 4const result = await request("GET /", { request: { fetch } });
Octokit.defaults
is now Octokit.withDefaults
Octokit.plugin
is now Octokit.withPlugins
. Instead of accepting one argument per plugin, the method now accepts a single array argument with all plugins to be applied.
@octokit/openapi-types
will be renamed to @octokit/types-openapi
to be consistents with the @octokit/types-*
prefixed packages that only contain types
@octokit/auth-token
: createTokenAuth()
no longer accepts a token
string argument, but requires options.token
.
plugins now receive all options passed to the Octokit
constructor as well as its defaults. Previously only the options passed to the constructor were passed
Octokit.DEFAULTS
octokit.options
request.defaults()
and endpoint.defaults()
with request.withDefaults()
and endpoint.withDefaults()
options.previews
from new Octokit(options)
packages/*
folders and release.plugins
configuration in package.json
are in syncscripts/types-rest-api-diff/update.js
- remove all package folders before re-creating, so that obsolete packages get removedoptions.auth
) are not set correctly when authStrategy
is set via .withDefaults({ authStrategy })
(#20)No vulnerabilities found.
Reason
14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
packaging workflow detected
Details
Reason
SAST tool is run on all commits
Details
Reason
security policy file detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
Found 1/27 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Score
Last Scanned on 2024-11-18
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