@times-components/interactive-wrapper
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@times-components/image | AI (dependencies): Internal sibling package from the same newsuk/times-components monorepo; expected dependency pattern across all versions. | ai |
Versions (showing 100 of 425)
| Version | Deps | Published |
|---|---|---|
| 0.9.154 | 3 / 15 | |
| 0.9.153 | 3 / 15 | |
| 0.9.152 | 3 / 15 | |
| 0.9.151 | 3 / 15 | |
| 0.9.150 | 3 / 15 | |
| 0.9.149 | 3 / 15 | |
| 0.9.148 | 3 / 15 | |
| 0.9.147 | 3 / 15 | |
| 0.9.146 | 3 / 15 | |
| 0.9.145 | 3 / 15 | |
| 0.9.144 | 3 / 15 | |
| 0.9.143 | 3 / 15 | |
| 0.9.142 | 3 / 15 | |
| 0.9.141 | 3 / 15 | |
| 0.9.140 | 3 / 15 | |
| 0.9.139 | 3 / 15 | |
| 0.9.138 | 3 / 15 | |
| 0.9.137 | 3 / 15 | |
| 0.9.136 | 3 / 15 | |
| 0.9.135 | 3 / 15 | |
| 0.9.134 | 3 / 15 | |
| 0.9.133 | 3 / 15 | |
| 0.9.132 | 3 / 15 | |
| 0.9.131 | 3 / 15 | |
| 0.9.130 | 3 / 15 | |
| 0.9.129 | 3 / 15 | |
| 0.9.128 | 3 / 15 | |
| 0.9.127 | 3 / 15 | |
| 0.9.126 | 3 / 15 | |
| 0.9.125 | 3 / 15 | |
| 0.9.124 | 3 / 15 | |
| 0.9.123 | 3 / 15 | |
| 0.9.122 | 3 / 15 | |
| 0.9.121 | 3 / 15 | |
| 0.9.120 | 3 / 15 | |
| 0.9.119 | 3 / 15 | |
| 0.9.118 | 3 / 15 | |
| 0.9.117 | 3 / 15 | |
| 0.9.116 | 3 / 15 | |
| 0.9.115 | 3 / 15 | |
| 0.9.114 | 3 / 15 | |
| 0.9.113 | 3 / 15 | |
| 0.9.112 | 3 / 15 | |
| 0.9.111 | 3 / 15 | |
| 0.9.110 | 3 / 15 | |
| 0.9.109 | 3 / 15 | |
| 0.9.108 | 3 / 15 | |
| 0.9.107 | 3 / 15 | |
| 0.9.106 | 3 / 15 | |
| 0.9.105 | 3 / 15 | |
| 0.9.104 | 3 / 15 | |
| 0.9.103 | 3 / 15 | |
| 0.9.102 | 3 / 15 | |
| 0.9.101 | 3 / 15 | |
| 0.9.100 | 3 / 15 | |
| 0.9.99 | 3 / 15 | |
| 0.9.98 | 3 / 15 | |
| 0.9.97 | 3 / 15 | |
| 0.9.96 | 3 / 15 | |
| 0.9.95 | 3 / 15 | |
| 0.9.94 | 3 / 15 | |
| 0.9.93 | 3 / 15 | |
| 0.9.92 | 3 / 15 | |
| 0.9.91 | 3 / 15 | |
| 0.9.90 | 2 / 15 | |
| 0.9.89 | 2 / 15 | |
| 0.9.88 | 2 / 15 | |
| 0.9.87 | 2 / 15 | |
| 0.9.86 | 2 / 15 | |
| 0.9.85 | 2 / 15 | |
| 0.9.84 | 2 / 15 | |
| 0.9.83 | 2 / 15 | |
| 0.9.82 | 2 / 15 | |
| 0.9.81 | 2 / 15 | |
| 0.9.80 | 2 / 15 | |
| 0.9.79 | 2 / 15 | |
| 0.9.78 | 2 / 15 | |
| 0.9.77 | 2 / 15 | |
| 0.9.76 | 2 / 15 | |
| 0.9.75 | 2 / 15 | |
| 0.9.74 | 2 / 15 | |
| 0.9.73 | 2 / 15 | |
| 0.9.72 | 2 / 15 | |
| 0.9.71 | 2 / 15 | |
| 0.9.70 | 2 / 15 | |
| 0.9.69 | 2 / 15 | |
| 0.9.68 | 2 / 15 | |
| 0.9.67 | 2 / 15 | |
| 0.9.66 | 2 / 15 | |
| 0.9.65 | 2 / 15 | |
| 0.9.64 | 2 / 15 | |
| 0.9.63 | 2 / 15 | |
| 0.9.62 | 2 / 15 | |
| 0.9.61 | 2 / 15 | |
| 0.9.60 | 2 / 15 | |
| 0.9.59 | 2 / 15 | |
| 0.9.58 | 2 / 15 | |
| 0.9.57 | 2 / 15 | |
| 0.9.56 | 2 / 15 | |
| 0.9.55 | 2 / 15 |
v0.9.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.