← Home

@commercelayer/cli-plugin-imports

npm Repository Homepage

Commerce Layer CLI Imports plugin

28
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

drpierlucommercelayer.io

Keywords

ecommerceclicommercelayer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@fast-csv/parse AI (phantom-deps): @fast-csv/parse is declared in dependencies and used in the plugin; phantom-dep heuristic misfires here. ai

Versions (showing 28 of 28)

Version Deps Published
4.4.6 10 / 17
4.4.5 10 / 17
4.4.4 10 / 17
4.4.3 10 / 17
4.4.2 10 / 17
4.4.1 10 / 17
4.4.0 10 / 17
4.3.1 10 / 17
4.3.0 10 / 17
4.2.15 10 / 18
4.2.14 10 / 18
4.2.13 10 / 18
4.2.12 10 / 18
4.2.11 10 / 18
4.2.10 10 / 18
4.2.9 10 / 18
4.2.8 10 / 18
4.2.7 10 / 18
4.2.6 10 / 18
4.2.5 10 / 18
4.2.4 10 / 18
4.2.3 10 / 18
4.2.2 10 / 18
4.2.1 10 / 18
4.2.0 10 / 18
4.1.2 9 / 18
4.1.0 9 / 18
4.0.0 9 / 18

v4.4.6

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.

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

v4.4.4

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.

v4.2.6

1 finding
LOW No provenance attestation provenance

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

v4.2.5

1 finding
LOW No provenance attestation provenance

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

v4.2.4

1 finding
LOW No provenance attestation provenance

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

v4.2.3

1 finding
LOW No provenance attestation provenance

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

v4.2.2

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.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: drpierlu → commercelayer.io (on 2024-05-20, known maintainer) provenance

This version was published by a different npm account (commercelayer.io) than the most recent previously approved version (drpierlu) on 2024-05-20, but commercelayer.io 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.

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.

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