← Home

@octokit-next/endpoint

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

gr2moctokit-next-bot

Keywords

octokitgithubapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): octokit-next-bot is the official Octokit automation account; transition from octokitbot is a documented org-level rename, not a takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): octokitbot removal is part of the same documented Octokit bot account transition; not indicative of a hostile takeover. ai
phantom-deps phantom-dep:type-fest AI (phantom-deps): type-fest is used as a TypeScript types-only dependency in .d.ts files; not directly imported in JS is expected and benign for this package. ai

Versions (showing 9 of 9)

Version Deps Published
3.0.0 4 / 0
2.5.1 4 / 0
2.3.1 4 / 0
2.3.0 4 / 0
2.2.0 4 / 0
2.1.1 4 / 0
2.1.0 4 / 0
2.0.1 4 / 0
2.0.0 4 / 0

v3.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.1

2 findings
HIGH Publisher changed: octokitbot → octokit-next-bot (on 2022-10-10) provenance

This version was published by a different npm account than previous versions on 2022-10-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

2 findings
HIGH Publisher changed: octokitbot → octokit-next-bot (on 2022-10-03) provenance

This version was published by a different npm account than previous versions on 2022-10-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.