← Home

@glimmer/util

npm Repository Homepage

Common utilities used in Glimmer

14
Versions
MIT
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

tomdalerwjbluedgeblockschancancodewycatschadhietalakrisseldenstefanpennermmunmixonicpzuraqglimmer-vm-github-actionsnullvoxpopulief4

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/prod/index.js AI (source-diff): Rollup-minified prod bundle, not obfuscation; canonical Glimmer build output. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): @glimmer/util is a legitimate scoped package in the glimmerjs ecosystem; Levenshtein match to uuid is a false positive. ai

Versions (showing 14 of 14)

Version Deps Published
0.94.8 1 / 9
0.94.7 1 / 9
0.94.6 1 / 9
0.94.5 1 / 9
0.94.4 1 / 9
0.94.3 1 / 9
0.94.2 1 / 9
0.94.1 1 / 9
0.94.0 1 / 9
0.93.1 2 / 9
0.93.0 2 / 9
0.92.3 2 / 7
0.92.2 2 / 7
0.92.1 2 / 7

v0.94.7

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.

v0.94.6

1 finding
LOW No provenance attestation provenance

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

v0.94.5

1 finding
LOW No provenance attestation provenance

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

v0.94.4

1 finding
LOW No provenance attestation provenance

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

v0.94.3

1 finding
LOW No provenance attestation provenance

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

v0.94.2

1 finding
LOW No provenance attestation provenance

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

v0.94.1

1 finding
LOW No provenance attestation provenance

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

v0.94.0

1 finding
LOW No provenance attestation provenance

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

v0.93.1

1 finding
LOW No provenance attestation provenance

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

v0.93.0

1 finding
LOW No provenance attestation provenance

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

v0.92.3

2 findings
HIGH New obfuscated file: dist/prod/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.92.2

2 findings
HIGH New obfuscated file: dist/prod/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.92.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.