@fundamental-ngx/datetime-adapter
Datetime adapter for SAP Fundamentals, based on Day.js package
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:esm2022/lib/dayjs-datetime-adapter.mjs | AI (source-diff): ESM bundle output for Angular library; sample shows plain readable code, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:esm2020/lib/dayjs-datetime-adapter.mjs | AI (source-diff): Angular compiled ESM output with ɵfac/ɵprov metadata triggers long-line heuristic; code is plaintext and readable. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SAP monorepo library; sparse README/keywords are a consistent pattern across all its sub-packages. | ai |
Versions (showing 100 of 207)
| Version | Deps | Published |
|---|---|---|
| 0.48.1 | 1 / 0 | |
| 0.48.0 | 1 / 0 | |
| 0.47.4 | 1 / 0 | |
| 0.47.3 | 1 / 0 | |
| 0.47.2 | 1 / 0 | |
| 0.47.1 | 1 / 0 | |
| 0.47.0 | 1 / 0 | |
| 0.46.1 | 1 / 0 | |
| 0.46.0 | 1 / 0 | |
| 0.45.1 | 1 / 0 | |
| 0.45.0 | 1 / 0 | |
| 0.44.0 | 1 / 0 | |
| 0.43.61 | 1 / 0 | |
| 0.43.60 | 1 / 0 | |
| 0.43.59 | 1 / 0 | |
| 0.43.58 | 1 / 0 | |
| 0.43.57 | 1 / 0 | |
| 0.43.56 | 1 / 0 | |
| 0.43.55 | 1 / 0 | |
| 0.43.54 | 1 / 0 | |
| 0.43.53 | 1 / 0 | |
| 0.43.52 | 1 / 0 | |
| 0.43.51 | 1 / 0 | |
| 0.43.50 | 1 / 0 | |
| 0.43.49 | 1 / 0 | |
| 0.43.48 | 1 / 0 | |
| 0.43.47 | 1 / 0 | |
| 0.43.46 | 1 / 0 | |
| 0.43.45 | 1 / 0 | |
| 0.43.44 | 1 / 0 | |
| 0.43.43 | 1 / 0 | |
| 0.43.42 | 1 / 0 | |
| 0.43.41 | 1 / 0 | |
| 0.43.40 | 1 / 0 | |
| 0.43.39 | 1 / 0 | |
| 0.43.38 | 1 / 0 | |
| 0.43.37 | 1 / 0 | |
| 0.43.36 | 1 / 0 | |
| 0.43.35 | 1 / 0 | |
| 0.43.34 | 1 / 0 | |
| 0.43.33 | 1 / 0 | |
| 0.43.32 | 1 / 0 | |
| 0.43.31 | 1 / 0 | |
| 0.43.30 | 1 / 0 | |
| 0.43.29 | 1 / 0 | |
| 0.43.28 | 1 / 0 | |
| 0.43.27 | 1 / 0 | |
| 0.43.26 | 1 / 0 | |
| 0.43.25 | 1 / 0 | |
| 0.43.24 | 1 / 0 | |
| 0.43.23 | 1 / 0 | |
| 0.43.22 | 1 / 0 | |
| 0.43.21 | 1 / 0 | |
| 0.43.20 | 1 / 0 | |
| 0.43.19 | 1 / 0 | |
| 0.43.18 | 1 / 0 | |
| 0.43.17 | 1 / 0 | |
| 0.43.16 | 1 / 0 | |
| 0.43.15 | 1 / 0 | |
| 0.43.14 | 1 / 0 | |
| 0.43.13 | 1 / 0 | |
| 0.43.12 | 1 / 0 | |
| 0.43.11 | 1 / 0 | |
| 0.43.10 | 1 / 0 | |
| 0.43.9 | 1 / 0 | |
| 0.43.8 | 1 / 0 | |
| 0.43.7 | 1 / 0 | |
| 0.43.6 | 1 / 0 | |
| 0.43.5 | 1 / 0 | |
| 0.43.4 | 1 / 0 | |
| 0.43.3 | 1 / 0 | |
| 0.43.2 | 1 / 0 | |
| 0.43.1 | 1 / 0 | |
| 0.43.0 | 1 / 0 | |
| 0.42.0 | 1 / 0 | |
| 0.41.0 | 1 / 0 | |
| 0.40.5 | 1 / 0 | |
| 0.40.4 | 1 / 0 | |
| 0.40.3 | 1 / 0 | |
| 0.40.2 | 1 / 0 | |
| 0.40.1 | 1 / 0 | |
| 0.40.0 | 1 / 0 | |
| 0.39.2 | 1 / 0 | |
| 0.39.1 | 1 / 0 | |
| 0.39.0 | 1 / 0 | |
| 0.38.6 | 1 / 0 | |
| 0.38.5 | 1 / 0 | |
| 0.38.4 | 1 / 0 | |
| 0.38.3 | 1 / 0 | |
| 0.38.2 | 1 / 0 | |
| 0.38.0 | 1 / 0 | |
| 0.37.3 | 1 / 0 | |
| 0.37.2 | 1 / 0 | |
| 0.37.1 | 1 / 0 | |
| 0.37.0 | 1 / 0 | |
| 0.36.4 | 1 / 0 | |
| 0.36.3 | 1 / 0 | |
| 0.36.2 | 1 / 0 | |
| 0.36.1 | 1 / 0 | |
| 0.36.0 | 1 / 0 |
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.