← Home

@slack/oauth

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

slackhqajmsgorbach0vstevegillslack_biztechmisscodedmwbrookscchenshsspencer-slackevegerise-zimfarhanjk

Keywords

slackoauthbothttpapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a TypeScript type package legitimately declared as a dependency for type availability; not directly imported by design. Stable pattern for this package. ai
phantom-deps phantom-dep:@types/jsonwebtoken AI (phantom-deps): @types/jsonwebtoken is a TypeScript type package legitimately declared as a dependency alongside jsonwebtoken. Not directly imported by design. Stable pattern for this package. ai

Versions (showing 7 of 7)

Version Deps Published
4.0.0 5 / 3
3.0.5 5 / 3
3.0.4 5 / 17
3.0.3 6 / 15
3.0.2 6 / 13
3.0.1 6 / 22
3.0.0 6 / 21

v4.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.

v3.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: slackhq → e-zim (on 2025-03-26, known maintainer) provenance

This version was published by a different npm account (e-zim) than the most recent previously approved version (slackhq) on 2025-03-26, but e-zim is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: e-zim → slackhq (on 2024-12-10, known maintainer) provenance

This version was published by a different npm account (slackhq) than the most recent previously approved version (e-zim) on 2024-12-10, but slackhq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.0.1

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.

v3.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.