← Home

@neovici/cosmoz-image-viewer

[![Build Status](https://travis-ci.org/Neovici/cosmoz-image-viewer.svg?branch=master)](https://travis-ci.org/Neovici/cosmoz-image-viewer)

21
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nomegocristineculawurpermegheaiulian

Keywords

web-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): i18next is a well-known, established package replacing a private cosmoz-i18next wrapper; not a suspicious addition. ai
publish-pattern dormant-publish AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; dormancy explained by org release cadence. ai
dependencies unvetted-dep:@neovici/cosmoz-tokens AI (dependencies): First-party @neovici ecosystem dependency; stable pattern for this package family. ai
dependencies unvetted-dep:@neovici/cosmoz-i18next AI (dependencies): First-party @neovici ecosystem dependency; stable pattern for this package family. ai
dependencies unvetted-dep:@neovici/cosmoz-utils AI (dependencies): First-party @neovici ecosystem dependency; stable pattern for this package family. ai
dependencies unvetted-dep:@pionjs/pion AI (dependencies): Known web-components utility used consistently across @neovici packages; no malicious signals. ai
dependencies unvetted-dep:@neovici/cosmoz-autocomplete AI (dependencies): First-party @neovici ecosystem dependency; stable pattern for this package family. ai
dependencies unvetted-dep:@neovici/cosmoz-slider AI (dependencies): First-party @neovici ecosystem dependency; stable pattern for this package family. ai

Versions (showing 21 of 21)

Version Deps Published
8.11.1 8 / 20
8.11.0 8 / 21
8.10.1 8 / 21
8.10.0 8 / 21
8.9.0 8 / 21
8.8.0 8 / 21
8.7.0 8 / 21
8.6.4 6 / 21
8.6.3 6 / 21
8.6.2 6 / 21
8.6.1 6 / 20
8.6.0 6 / 20
8.5.0 6 / 20
8.4.1 6 / 20
8.4.0 6 / 19
8.3.2 6 / 19
8.2.1 6 / 22
8.2.0 6 / 22
8.1.1 6 / 22
8.1.0 6 / 22
8.0.0 6 / 11

v8.11.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.

v8.11.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.

v8.10.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.

v8.9.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.

v8.8.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.

v8.6.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.

v8.6.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.

v8.1.1

1 finding
LOW No provenance attestation provenance

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

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

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