@wisemen/datewise
A comprehensive TypeScript library for working with dates, times, and ranges in a type-safe and immutable way. Built on top of Day.js, it provides specialized types and utilities for temporal operations with strong TypeORM integration.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@wisemen/quantity | AI (dependencies): Same-org monorepo dependency; consistent publisher pattern across @wisemen/* packages. | ai | |
| dependencies | unvetted-dep:@wisemen/pagination | AI (dependencies): Same-org monorepo dependency; consistent publisher pattern across @wisemen/* packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.1.12 | 2 / 6 | |
| 0.1.7 | 2 / 6 | |
| 0.1.3 | 0 / 8 | |
| 0.1.2 | 0 / 8 | |
| 0.1.1 | 0 / 8 | |
| 0.1.0 | 0 / 8 | |
| 0.0.17 | 0 / 8 | |
| 0.0.16 | 0 / 8 | |
| 0.0.15 | 0 / 8 | |
| 0.0.14 | 0 / 8 | |
| 0.0.13 | 0 / 8 | |
| 0.0.12 | 0 / 8 | |
| 0.0.11 | 0 / 8 | |
| 0.0.10 | 0 / 8 | |
| 0.0.9 | 0 / 8 | |
| 0.0.8 | 0 / 8 | |
| 0.0.7 | 0 / 8 | |
| 0.0.6 | 0 / 8 | |
| 0.0.5 | 0 / 8 | |
| 0.0.4 | 0 / 8 | |
| 0.0.3 | 0 / 8 | |
| 0.0.2 | 0 / 8 | |
| 0.0.1 | 0 / 8 |
v0.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.