← Home

@swissquote/crafty-preset-postcss

npm Repository Homepage

<table> <tr><th>Compatible Runners</th><td>

15
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

david.joaquimmofleurystephane.goetz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Config-loader pattern in a build tool; loads user-supplied config paths by design, stable across versions. ai
phantom-deps phantom-dep:@swissquote/crafty AI (phantom-deps): Same-org monorepo package; loaded by convention rather than direct import. ai
phantom-deps phantom-dep:schema-utils AI (phantom-deps): Used via config/webpack integration layer, not direct import; stable false positive for this package. ai
phantom-deps phantom-dep:@babel/code-frame AI (phantom-deps): Framework-scoped package loaded by convention in build tooling; stable false positive. ai

Versions (showing 15 of 15)

Version Deps Published
1.30.1 10 / 6
1.30.0 10 / 6
1.29.0 10 / 6
1.28.1 10 / 6
1.28.0 10 / 6
1.27.0 10 / 6
1.26.0 10 / 6
1.24.0 10 / 6
1.23.0 10 / 6
1.22.3 10 / 6
1.22.2 10 / 6
1.22.1 10 / 6
1.22.0 10 / 6
1.18.1 11 / 8
1.18.0 11 / 8

v1.28.0

1 finding
LOW No provenance attestation provenance

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

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

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

v1.24.0

1 finding
LOW No provenance attestation provenance

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

v1.23.0

1 finding
LOW No provenance attestation provenance

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

v1.22.3

1 finding
LOW No provenance attestation provenance

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

v1.22.2

1 finding
LOW No provenance attestation provenance

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

v1.22.1

1 finding
LOW No provenance attestation provenance

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

v1.22.0

1 finding
LOW No provenance attestation provenance

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

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

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