@times-components/message-bar
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance not used across the @times-components ecosystem. | ai |
Versions (showing 100 of 158)
| Version | Deps | Published |
|---|---|---|
| 0.7.149 | 6 / 14 | |
| 0.7.148 | 6 / 14 | |
| 0.7.147 | 6 / 14 | |
| 0.7.146 | 6 / 14 | |
| 0.7.145 | 6 / 14 | |
| 0.7.144 | 6 / 14 | |
| 0.7.143 | 6 / 14 | |
| 0.7.142 | 6 / 14 | |
| 0.7.141 | 6 / 14 | |
| 0.7.140 | 6 / 14 | |
| 0.7.139 | 6 / 14 | |
| 0.7.138 | 6 / 14 | |
| 0.7.137 | 6 / 14 | |
| 0.7.136 | 6 / 14 | |
| 0.7.135 | 6 / 14 | |
| 0.7.134 | 6 / 14 | |
| 0.7.133 | 6 / 14 | |
| 0.7.132 | 6 / 14 | |
| 0.7.131 | 6 / 14 | |
| 0.7.130 | 6 / 14 | |
| 0.7.129 | 6 / 14 | |
| 0.7.128 | 6 / 14 | |
| 0.7.127 | 6 / 14 | |
| 0.7.126 | 6 / 14 | |
| 0.7.125 | 6 / 14 | |
| 0.7.124 | 6 / 14 | |
| 0.7.123 | 6 / 14 | |
| 0.7.122 | 6 / 14 | |
| 0.7.121 | 6 / 14 | |
| 0.7.120 | 6 / 14 | |
| 0.7.119 | 6 / 14 | |
| 0.7.118 | 6 / 14 | |
| 0.7.117 | 6 / 14 | |
| 0.7.116 | 6 / 14 | |
| 0.7.115 | 6 / 14 | |
| 0.7.114 | 6 / 14 | |
| 0.7.113 | 6 / 14 | |
| 0.7.112 | 6 / 14 | |
| 0.7.111 | 6 / 14 | |
| 0.7.110 | 6 / 14 | |
| 0.7.109 | 6 / 14 | |
| 0.7.108 | 6 / 14 | |
| 0.7.107 | 6 / 14 | |
| 0.7.106 | 6 / 14 | |
| 0.7.105 | 6 / 14 | |
| 0.7.104 | 6 / 14 | |
| 0.7.103 | 6 / 14 | |
| 0.7.102 | 6 / 14 | |
| 0.7.101 | 6 / 14 | |
| 0.7.100 | 6 / 14 | |
| 0.7.99 | 6 / 14 | |
| 0.7.98 | 6 / 14 | |
| 0.7.97 | 6 / 14 | |
| 0.7.96 | 6 / 14 | |
| 0.7.95 | 6 / 14 | |
| 0.7.94 | 6 / 14 | |
| 0.7.93 | 6 / 14 | |
| 0.7.92 | 6 / 14 | |
| 0.7.91 | 6 / 14 | |
| 0.7.90 | 6 / 14 | |
| 0.7.89 | 6 / 14 | |
| 0.7.88 | 6 / 14 | |
| 0.7.87 | 6 / 14 | |
| 0.7.86 | 6 / 14 | |
| 0.7.85 | 6 / 14 | |
| 0.7.84 | 6 / 14 | |
| 0.7.83 | 6 / 14 | |
| 0.7.82 | 6 / 14 | |
| 0.7.81 | 6 / 14 | |
| 0.7.80 | 6 / 14 | |
| 0.7.79 | 6 / 14 | |
| 0.7.78 | 6 / 14 | |
| 0.7.77 | 6 / 14 | |
| 0.7.76 | 6 / 14 | |
| 0.7.75 | 6 / 14 | |
| 0.7.74 | 6 / 14 | |
| 0.7.73 | 6 / 14 | |
| 0.7.72 | 6 / 14 | |
| 0.7.71 | 6 / 14 | |
| 0.7.70 | 6 / 14 | |
| 0.7.69 | 6 / 14 | |
| 0.7.68 | 6 / 14 | |
| 0.7.67 | 6 / 14 | |
| 0.7.66 | 6 / 14 | |
| 0.7.65 | 6 / 14 | |
| 0.7.64 | 6 / 14 | |
| 0.7.63 | 6 / 14 | |
| 0.7.62 | 6 / 14 | |
| 0.7.61 | 6 / 14 | |
| 0.7.60 | 6 / 14 | |
| 0.7.59 | 6 / 14 | |
| 0.7.58 | 6 / 14 | |
| 0.7.57 | 6 / 14 | |
| 0.7.56 | 6 / 14 | |
| 0.7.55 | 6 / 14 | |
| 0.7.54 | 6 / 14 | |
| 0.7.53 | 6 / 14 | |
| 0.7.52 | 6 / 14 | |
| 0.7.51 | 6 / 14 | |
| 0.7.50 | 6 / 14 |
v0.7.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.