← Home

@times-components/key-facts

Bulleted list of text data

100
Versions
BSD-3-Clause
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

marcincubernewsuknews-tools

Keywords

reactwebkey-factscomponent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@times-components/utils AI (dependencies): Same-org monorepo sibling; stable pattern across all @times-components versions. ai
dependencies unvetted-dep:@times-components/responsive AI (dependencies): Same-org monorepo sibling; stable pattern across all @times-components versions. ai
dependencies unvetted-dep:@times-components/ts-components AI (dependencies): Same-org monorepo sibling; stable pattern across all @times-components versions. ai
dependencies unvetted-dep:@times-components/ts-styleguide AI (dependencies): Same-org monorepo sibling; stable pattern across all @times-components versions. ai
provenance no-provenance AI (provenance): Long-established monorepo package; no provenance is consistent across all versions of this package family. ai

Versions (showing 100 of 305)

Version Deps Published
2.13.135 8 / 18
2.13.134 8 / 18
2.13.133 8 / 18
2.13.132 8 / 18
2.13.131 8 / 18
2.13.130 8 / 18
2.13.129 8 / 18
2.13.128 8 / 18
2.13.127 8 / 18
2.13.126 8 / 18
2.13.125 8 / 18
2.13.124 8 / 18
2.13.123 8 / 18
2.13.122 8 / 18
2.13.121 8 / 18
2.13.120 8 / 18
2.13.119 8 / 18
2.13.118 8 / 18
2.13.117 8 / 18
2.13.115 8 / 18
2.13.114 8 / 18
2.13.113 8 / 18
2.13.112 8 / 18
2.13.111 8 / 18
2.13.110 8 / 18
2.13.108 8 / 18
2.13.107 8 / 18
2.13.105 8 / 18
2.13.102 8 / 18
2.13.101 8 / 18
2.13.65 8 / 18
2.13.53 8 / 18
2.13.52 8 / 18
2.13.51 8 / 18
2.13.50 8 / 18
2.13.49 8 / 18
2.13.48 8 / 18
2.13.47 8 / 18
2.13.46 8 / 18
2.13.45 8 / 18
2.13.44 8 / 18
2.13.43 8 / 18
2.13.42 8 / 18
2.13.41 8 / 18
2.13.40 8 / 18
2.13.39 8 / 18
2.13.38 8 / 18
2.13.37 8 / 18
2.13.36 8 / 18
2.13.35 8 / 18
2.13.34 8 / 18
2.13.33 8 / 18
2.13.32 8 / 18
2.13.31 8 / 18
2.13.30 8 / 18
2.13.29 8 / 18
2.13.28 8 / 18
2.13.27 8 / 18
2.13.26 8 / 18
2.13.25 8 / 18
2.13.24 8 / 18
2.13.23 8 / 18
2.13.22 8 / 18
2.13.21 8 / 18
2.13.20 8 / 18
2.13.18 8 / 18
2.13.17 8 / 18
2.13.16 8 / 18
2.13.15 8 / 18
2.13.14 8 / 18
2.13.13 8 / 18
2.13.12 8 / 18
2.13.11 8 / 18
2.13.10 8 / 18
2.13.9 8 / 18
2.13.8 8 / 18
2.13.7 8 / 18
2.13.6 8 / 18
2.13.5 8 / 18
2.13.4 8 / 18
2.13.3 8 / 18
2.13.2 8 / 18
2.13.1 8 / 18
2.13.0 8 / 18
2.12.125 8 / 18
2.12.124 8 / 18
2.12.123 8 / 18
2.12.122 8 / 18
2.12.121 8 / 18
2.12.120 8 / 18
2.12.119 8 / 18
2.12.118 8 / 18
2.12.117 8 / 18
2.12.116 8 / 18
2.12.115 8 / 18
2.12.114 8 / 18
2.12.113 8 / 18
2.12.112 8 / 18
2.12.111 8 / 18
2.12.110 8 / 18
Showing 100 of 305 Next page →

v2.13.135

1 finding
INFO No provenance attestation provenance

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

v2.13.134

1 finding
INFO No provenance attestation provenance

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

v2.13.133

1 finding
INFO No provenance attestation provenance

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

v2.13.132

1 finding
INFO No provenance attestation provenance

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

v2.13.131

1 finding
INFO No provenance attestation provenance

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

v2.13.23

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.

v2.13.22

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.

v2.13.21

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.

v2.13.20

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.

v2.13.18

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.

v2.13.17

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.

v2.13.16

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.

v2.13.15

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.

v2.13.14

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.

v2.13.13

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.

v2.13.12

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.

v2.13.11

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.

v2.13.10

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.

v2.13.9

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.

v2.13.8

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.

v2.13.7

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.

v2.13.6

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.

v2.13.5

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.

v2.13.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.

v2.13.3

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.

v2.13.2

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.

v2.13.1

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.

v2.13.0

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.

v2.12.125

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.

v2.12.124

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.

v2.12.123

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.

v2.12.122

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.

v2.12.121

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.

v2.12.120

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.

v2.12.119

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.

v2.12.118

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.

v2.12.117

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.

v2.12.116

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.

v2.12.115

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.

v2.12.114

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.

v2.12.113

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.

v2.12.112

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.

v2.12.111

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.

v2.12.110

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.