← Home

@qui-cli/env

npm Repository Homepage

@qui-cli Plugin: Standardized environment configuration

10
Versions
GPL-3.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

battis

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@1password/sdk AI (phantom-deps): 1Password SDK is a runtime dep used conditionally; phantom-dep heuristic fires on config references, not a real missing import. ai
phantom-deps phantom-dep:@battis/import-package-json AI (phantom-deps): Same-author dep; phantom-dep heuristic fires on config references, stable false positive for this package. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @qui-cli/env is part of a CLI plugin suite; Levenshtein match to 'ajv' is coincidental. ai

Versions (showing 10 of 10)

Version Deps Published
5.2.0 3 / 11
5.1.2 3 / 6
5.1.1 3 / 12
5.1.0 3 / 12
5.0.4 3 / 8
5.0.3 3 / 8
5.0.2 3 / 8
5.0.1 3 / 8
5.0.0 3 / 8
4.1.0 3 / 8

v5.1.2

1 finding
LOW No provenance attestation provenance

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

v5.1.1

1 finding
LOW No provenance attestation provenance

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

v5.0.4

1 finding
LOW No provenance attestation provenance

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

v5.0.3

1 finding
LOW No provenance attestation provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

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