@peerbit/clock-service
Clock signing
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with 595 versions; sparse metadata is typical for internal packages in this ecosystem. | ai |
Versions (showing 100 of 244)
| Version | Deps | Published |
|---|---|---|
| 3.0.147 | 3 / 1 | |
| 3.0.145 | 3 / 1 | |
| 3.0.144 | 3 / 1 | |
| 3.0.143 | 3 / 1 | |
| 3.0.142 | 3 / 1 | |
| 3.0.141 | 3 / 1 | |
| 3.0.140 | 3 / 1 | |
| 3.0.139 | 3 / 1 | |
| 3.0.138 | 3 / 1 | |
| 3.0.137 | 3 / 1 | |
| 3.0.136 | 3 / 1 | |
| 3.0.135 | 3 / 1 | |
| 3.0.134 | 3 / 1 | |
| 3.0.133 | 3 / 1 | |
| 3.0.132 | 3 / 1 | |
| 3.0.130 | 3 / 1 | |
| 3.0.129 | 3 / 1 | |
| 3.0.128 | 3 / 1 | |
| 3.0.127 | 3 / 1 | |
| 3.0.126 | 3 / 1 | |
| 3.0.125 | 3 / 1 | |
| 3.0.124 | 3 / 1 | |
| 3.0.123 | 3 / 1 | |
| 3.0.122 | 3 / 1 | |
| 3.0.121 | 3 / 1 | |
| 3.0.120 | 3 / 1 | |
| 3.0.119 | 3 / 1 | |
| 3.0.118 | 3 / 1 | |
| 3.0.117 | 3 / 1 | |
| 3.0.116 | 3 / 1 | |
| 3.0.115 | 3 / 1 | |
| 3.0.114 | 3 / 1 | |
| 3.0.113 | 3 / 1 | |
| 3.0.112 | 3 / 1 | |
| 3.0.111 | 3 / 1 | |
| 3.0.110 | 3 / 1 | |
| 3.0.109 | 3 / 1 | |
| 3.0.108 | 3 / 1 | |
| 3.0.107 | 3 / 1 | |
| 3.0.106 | 3 / 1 | |
| 3.0.105 | 3 / 1 | |
| 3.0.104 | 3 / 1 | |
| 3.0.103 | 3 / 1 | |
| 3.0.102 | 3 / 1 | |
| 3.0.101 | 3 / 1 | |
| 3.0.100 | 3 / 1 | |
| 3.0.99 | 3 / 1 | |
| 3.0.98 | 3 / 1 | |
| 3.0.97 | 3 / 1 | |
| 3.0.96 | 3 / 1 | |
| 3.0.95 | 3 / 1 | |
| 3.0.94 | 3 / 1 | |
| 3.0.93 | 3 / 1 | |
| 3.0.92 | 3 / 1 | |
| 3.0.91 | 3 / 1 | |
| 3.0.90 | 3 / 1 | |
| 3.0.89 | 3 / 1 | |
| 3.0.88 | 3 / 1 | |
| 3.0.87 | 3 / 1 | |
| 3.0.86 | 3 / 1 | |
| 3.0.85 | 3 / 1 | |
| 3.0.84 | 3 / 1 | |
| 3.0.83 | 3 / 1 | |
| 3.0.82 | 3 / 1 | |
| 3.0.81 | 3 / 1 | |
| 3.0.80 | 3 / 1 | |
| 3.0.79 | 3 / 1 | |
| 3.0.78 | 3 / 1 | |
| 3.0.77 | 3 / 1 | |
| 3.0.76 | 3 / 1 | |
| 3.0.75 | 3 / 1 | |
| 3.0.74 | 3 / 1 | |
| 3.0.73 | 3 / 1 | |
| 3.0.72 | 3 / 1 | |
| 3.0.71 | 3 / 1 | |
| 3.0.70 | 3 / 1 | |
| 3.0.69 | 3 / 1 | |
| 3.0.68 | 3 / 1 | |
| 3.0.67 | 3 / 1 | |
| 3.0.66 | 3 / 1 | |
| 3.0.65 | 3 / 1 | |
| 3.0.64 | 3 / 1 | |
| 3.0.63 | 3 / 1 | |
| 3.0.62 | 3 / 1 | |
| 3.0.61 | 3 / 1 | |
| 3.0.60 | 3 / 1 | |
| 3.0.59 | 3 / 1 | |
| 3.0.58 | 3 / 1 | |
| 3.0.57 | 3 / 1 | |
| 3.0.56 | 3 / 1 | |
| 3.0.55 | 3 / 1 | |
| 3.0.54 | 3 / 1 | |
| 3.0.53 | 3 / 1 | |
| 3.0.52 | 3 / 1 | |
| 3.0.51 | 3 / 1 | |
| 3.0.50 | 3 / 1 | |
| 3.0.49 | 3 / 1 | |
| 3.0.48 | 3 / 1 | |
| 3.0.47 | 3 / 1 | |
| 3.0.46 | 3 / 1 |
v3.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.