← Home

@discordjs/util

6
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

crawlhydrabolt

Keywords

apibotclientnodediscordjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Official discordjs monorepo publish; gitHead absence is benign env change. ai
provenance no-provenance AI (provenance): No provenance is not a risk for this trusted package. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): @discordjs/util is the official discord.js utility package under the @discordjs npm scope; Levenshtein match against 'uuid' is a false positive with no impersonation intent. ai
dependencies unvetted-dep:discord-api-types AI (dependencies): discord-api-types is the canonical Discord API type definitions package and a natural, expected dependency for any @discordjs/* package. ai

Versions (showing 6 of 6)

Version Deps Published
1.2.0 1 / 16
1.1.1 0 / 16
1.1.0 0 / 16
1.0.2 0 / 14
1.0.1 0 / 14
1.0.0 0 / 14

v1.1.1

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.

v1.1.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.

v1.0.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crawl.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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