← Home

@shopgate/pwa-core

39
Versions
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

pvomhoffshopgate-publisherzrgrvshmfriedewald

Keywords

pwacoreconnect-libraryshopgateconnect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:lodash AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. ai
phantom-deps phantom-dep:detector AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. ai
phantom-deps phantom-dep:crypto-js AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. ai
phantom-deps phantom-dep:mobile-detect AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. ai
phantom-deps phantom-dep:isomorphic-fetch AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. ai
provenance no-provenance AI (provenance): Long-established package; no provenance is consistent across all versions and is not a risk indicator here. ai

Versions (showing 39 of 39)

Version Deps Published
7.31.4 4 / 1
7.31.3 4 / 1
7.31.2 4 / 1
7.31.1 4 / 1
7.31.0 4 / 1
7.30.5 4 / 0
7.30.4 4 / 0
7.30.3 4 / 0
7.30.2 4 / 0
7.30.1 4 / 0
7.30.0 4 / 0
7.29.9 5 / 0
7.29.8 5 / 0
7.29.7 5 / 0
7.29.6 5 / 0
7.29.5 5 / 0
7.29.4 5 / 0
7.29.3 5 / 0
7.29.1 5 / 0
7.29.0 5 / 0
7.28.3 5 / 0
7.28.2 5 / 0
7.28.1 5 / 0
7.28.0 5 / 0
7.27.5 5 / 0
7.27.4 5 / 0
7.27.3 5 / 0
7.27.2 5 / 0
7.27.1 5 / 0
7.27.0 5 / 0
7.26.0 5 / 0
7.25.1 5 / 0
7.24.8 5 / 0
7.12.9 5 / 0
7.12.8 5 / 0
7.12.7 5 / 0
7.12.6 5 / 0
7.12.5 5 / 0
7.12.4 5 / 0

v7.31.4

1 finding
INFO No provenance attestation provenance

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

v7.31.3

1 finding
INFO No provenance attestation provenance

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

v7.31.2

1 finding
INFO No provenance attestation provenance

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

v7.31.1

1 finding
INFO No provenance attestation provenance

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

v7.12.9

1 finding
INFO No provenance attestation provenance

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

v7.12.8

1 finding
INFO No provenance attestation provenance

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

v7.12.7

1 finding
INFO No provenance attestation provenance

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

v7.12.6

1 finding
INFO No provenance attestation provenance

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

v7.12.5

1 finding
INFO No provenance attestation provenance

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

v7.12.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.