@live-change/uid
Simple unique id generator with timestamp and source
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @live-change package with 413 versions; not a typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @live-change package; name similarity to zod is coincidental. | ai |
Versions (showing 100 of 340)
| Version | Deps | Published |
|---|---|---|
| 0.9.110 | 0 / 0 | |
| 0.9.109 | 0 / 0 | |
| 0.9.108 | 0 / 0 | |
| 0.9.107 | 0 / 0 | |
| 0.9.106 | 0 / 0 | |
| 0.9.105 | 0 / 0 | |
| 0.9.104 | 0 / 0 | |
| 0.9.103 | 0 / 0 | |
| 0.9.102 | 0 / 0 | |
| 0.9.101 | 0 / 0 | |
| 0.9.100 | 0 / 0 | |
| 0.9.99 | 0 / 0 | |
| 0.9.98 | 0 / 0 | |
| 0.9.97 | 0 / 0 | |
| 0.9.96 | 0 / 0 | |
| 0.9.95 | 0 / 0 | |
| 0.9.94 | 0 / 0 | |
| 0.9.93 | 0 / 0 | |
| 0.9.92 | 0 / 0 | |
| 0.9.91 | 0 / 0 | |
| 0.9.90 | 0 / 0 | |
| 0.9.89 | 0 / 0 | |
| 0.9.88 | 0 / 0 | |
| 0.9.87 | 0 / 0 | |
| 0.9.86 | 0 / 0 | |
| 0.9.85 | 0 / 0 | |
| 0.9.84 | 0 / 0 | |
| 0.9.83 | 0 / 0 | |
| 0.9.82 | 0 / 0 | |
| 0.9.81 | 0 / 0 | |
| 0.9.80 | 0 / 0 | |
| 0.9.79 | 0 / 0 | |
| 0.9.78 | 0 / 0 | |
| 0.9.77 | 0 / 0 | |
| 0.9.76 | 0 / 0 | |
| 0.9.75 | 0 / 0 | |
| 0.9.74 | 0 / 0 | |
| 0.9.73 | 0 / 0 | |
| 0.9.72 | 0 / 0 | |
| 0.9.71 | 0 / 0 | |
| 0.9.70 | 0 / 0 | |
| 0.9.69 | 0 / 0 | |
| 0.9.68 | 0 / 0 | |
| 0.9.67 | 0 / 0 | |
| 0.9.66 | 0 / 0 | |
| 0.9.65 | 0 / 0 | |
| 0.9.64 | 0 / 0 | |
| 0.9.63 | 0 / 0 | |
| 0.9.62 | 0 / 0 | |
| 0.9.61 | 0 / 0 | |
| 0.9.60 | 0 / 0 | |
| 0.9.59 | 0 / 0 | |
| 0.9.58 | 0 / 0 | |
| 0.9.57 | 0 / 0 | |
| 0.9.56 | 0 / 0 | |
| 0.9.55 | 0 / 0 | |
| 0.9.54 | 0 / 0 | |
| 0.9.53 | 0 / 0 | |
| 0.9.52 | 0 / 0 | |
| 0.9.51 | 0 / 0 | |
| 0.9.50 | 0 / 0 | |
| 0.9.49 | 0 / 0 | |
| 0.9.48 | 0 / 0 | |
| 0.9.47 | 0 / 0 | |
| 0.9.46 | 0 / 0 | |
| 0.9.45 | 0 / 0 | |
| 0.9.44 | 0 / 0 | |
| 0.9.43 | 0 / 0 | |
| 0.9.42 | 0 / 0 | |
| 0.9.41 | 0 / 0 | |
| 0.9.40 | 0 / 0 | |
| 0.9.39 | 0 / 0 | |
| 0.9.38 | 0 / 0 | |
| 0.9.37 | 0 / 0 | |
| 0.9.36 | 0 / 0 | |
| 0.9.35 | 0 / 0 | |
| 0.9.34 | 0 / 0 | |
| 0.9.33 | 0 / 0 | |
| 0.9.32 | 0 / 0 | |
| 0.9.31 | 0 / 0 | |
| 0.9.30 | 0 / 0 | |
| 0.9.29 | 0 / 0 | |
| 0.9.28 | 0 / 0 | |
| 0.9.27 | 0 / 0 | |
| 0.9.26 | 0 / 0 | |
| 0.9.25 | 0 / 0 | |
| 0.9.24 | 0 / 0 | |
| 0.9.23 | 0 / 0 | |
| 0.9.22 | 0 / 0 | |
| 0.9.21 | 0 / 0 | |
| 0.9.20 | 0 / 0 | |
| 0.9.19 | 0 / 0 | |
| 0.9.18 | 0 / 0 | |
| 0.9.17 | 0 / 0 | |
| 0.9.16 | 0 / 0 | |
| 0.9.15 | 0 / 0 | |
| 0.9.14 | 0 / 0 | |
| 0.9.13 | 0 / 0 | |
| 0.9.12 | 0 / 0 | |
| 0.9.11 | 0 / 0 |
v0.9.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.9.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.