@thzero/library_common
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dayjs-plugin-utc | AI (phantom-deps): dayjs-plugin-utc is declared as a dep and used via config/plugin registration, not direct import; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.18.25 | 4 / 0 | |
| 0.18.23 | 4 / 0 | |
| 0.18.22 | 4 / 0 | |
| 0.18.21 | 4 / 0 | |
| 0.18.18 | 4 / 0 | |
| 0.18.17 | 4 / 0 | |
| 0.18.16 | 4 / 0 | |
| 0.18.14 | 4 / 0 | |
| 0.18.13 | 4 / 0 | |
| 0.18.12 | 4 / 0 | |
| 0.18.11 | 4 / 0 | |
| 0.18.10 | 4 / 0 | |
| 0.18.9 | 4 / 0 | |
| 0.18.8 | 4 / 0 | |
| 0.18.7 | 4 / 0 | |
| 0.18.6 | 4 / 0 | |
| 0.18.5 | 4 / 0 | |
| 0.18.4 | 4 / 0 |
v0.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.