← Home

@vendure/ui-devkit

npm Repository Homepage

A library for authoring Vendure Admin UI extensions

51
Versions
GPL-3.0-or-later
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

michaelbromleyvendure_teamdlhckhousein_is_programming

Keywords

vendurejavascriptextensions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Used in compiler/compile.js to run Angular CLI build commands — expected for a UI compilation toolkit. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads tsconfig.json by file path for modification — benign build-tool pattern, not arbitrary module loading. ai
phantom-deps phantom-dep:@angular/cli AI (phantom-deps): Angular CLI is a framework-convention dep invoked via child_process, not directly imported. ai
phantom-deps phantom-dep:@angular/compiler AI (phantom-deps): Angular compiler loaded by framework convention, not direct import. ai
phantom-deps phantom-dep:@angular/compiler-cli AI (phantom-deps): Angular compiler-cli loaded by framework convention, not direct import. ai
phantom-deps phantom-dep:@angular-devkit/build-angular AI (phantom-deps): Referenced in Angular config files by convention, not directly imported. ai

Versions (showing 51 of 53)

View all versions
Version Deps Published
3.7.1 11 / 11
3.7.0 11 / 11
3.6.5 11 / 11
3.6.4 11 / 11
3.6.3 11 / 11
3.6.2 11 / 11
3.6.1 11 / 11
3.6.0 11 / 11
3.5.6 11 / 11
3.5.5 11 / 11
3.5.4 11 / 11
3.5.3 11 / 11
3.5.2 11 / 11
3.5.1 11 / 11
3.5.0 11 / 11
3.4.4 11 / 11
3.4.3 11 / 11
3.4.2 11 / 11
3.4.1 11 / 11
3.4.0 11 / 11
3.3.8 11 / 11
3.3.7 11 / 11
3.3.6 11 / 11
3.3.5 11 / 11
3.3.4 11 / 11
3.3.3 11 / 11
3.3.2 11 / 11
3.3.1 11 / 11
3.3.0 11 / 11
3.2.4 11 / 11
3.2.3 11 / 11
3.2.2 11 / 11
3.2.1 11 / 11
3.2.0 11 / 11
3.1.8 11 / 11
3.1.7 11 / 11
3.1.6 11 / 11
3.1.5 11 / 11
3.1.4 11 / 11
3.1.3 11 / 11
3.1.2 11 / 11
3.1.1 11 / 11
3.1.0 11 / 11
3.0.8 11 / 11
3.0.7 11 / 11
3.0.6 11 / 11
3.0.5 11 / 11
3.0.4 11 / 11
3.0.3 11 / 11
3.0.2 11 / 11
3.0.1 11 / 11

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

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

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

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

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.8

1 finding
LOW No provenance attestation provenance

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

v3.1.7

1 finding
LOW No provenance attestation provenance

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

v3.1.6

1 finding
LOW No provenance attestation provenance

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

v3.1.5

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

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.