@eka-care/ekascribe-ts-sdk
EkaScribe TypeScript SDK - Modern ES2020 build
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared runtime dep; likely used in bundled/worker code not directly imported at top level. | ai | |
| phantom-deps | phantom-dep:lamejs | AI (phantom-deps): Declared runtime dep; used in audio encoding worker code, not a direct top-level import. | ai | |
| phantom-deps | phantom-dep:@ffmpeg/util | AI (phantom-deps): Declared runtime dep; used alongside @ffmpeg/ffmpeg in worker/bundled code. | ai | |
| phantom-deps | phantom-dep:@ffmpeg/ffmpeg | AI (phantom-deps): Declared runtime dep; used in ffmpeg worker code, not a direct top-level import. | ai | |
| phantom-deps | phantom-dep:@types/chrome | AI (phantom-deps): Type-only package for Chrome extension APIs; framework-scoped, not directly imported. | ai |
Versions (showing 47 of 147)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 0 / 0 | |
| 2.0.6 | 0 / 0 | |
| 2.0.5 | 0 / 0 | |
| 2.0.4 | 0 / 0 | |
| 2.0.3 | 0 / 0 | |
| 2.0.2 | 0 / 0 | |
| 2.0.0 | 0 / 0 | |
| 1.6.0 | 9 / 7 | |
| 1.5.86 | 9 / 6 | |
| 1.5.85 | 9 / 6 | |
| 1.5.83 | 9 / 7 | |
| 1.5.82 | 9 / 7 | |
| 1.5.81 | 9 / 6 | |
| 1.5.80 | 9 / 7 | |
| 1.5.79 | 9 / 6 | |
| 1.5.78 | 9 / 6 | |
| 1.5.77 | 9 / 6 | |
| 1.5.76 | 9 / 6 | |
| 1.5.75 | 9 / 6 | |
| 1.5.74 | 9 / 6 | |
| 1.5.73 | 9 / 6 | |
| 1.5.72 | 9 / 6 | |
| 1.5.71 | 9 / 6 | |
| 1.5.70 | 9 / 6 | |
| 1.5.69 | 9 / 6 | |
| 1.5.68 | 9 / 6 | |
| 1.5.67 | 9 / 6 | |
| 1.5.66 | 9 / 6 | |
| 1.5.65 | 9 / 6 | |
| 1.5.64 | 9 / 6 | |
| 1.5.63 | 9 / 6 | |
| 1.5.62 | 9 / 6 | |
| 1.5.60 | 9 / 6 | |
| 1.5.59 | 9 / 6 | |
| 1.5.58 | 9 / 6 | |
| 1.5.57 | 9 / 6 | |
| 1.5.56 | 9 / 6 | |
| 1.5.55 | 9 / 6 | |
| 1.5.54 | 9 / 6 | |
| 1.5.53 | 9 / 6 | |
| 1.5.52 | 9 / 6 | |
| 1.5.51 | 9 / 6 | |
| 1.5.50 | 9 / 6 | |
| 1.5.49 | 9 / 6 | |
| 1.5.47 | 9 / 6 | |
| 1.5.46 | 9 / 6 | |
| 1.5.45 | 9 / 6 |
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.