@blocklet/dataset-sdk
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:openapi-enforcer | AI (dependencies): openapi-enforcer is a legitimate OpenAPI validation library; stable dependency for this SDK package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Declared in dependencies; used via config/convention in this SDK package. | ai | |
| phantom-deps | phantom-dep:ufo | AI (phantom-deps): Declared in dependencies; SDK re-export pattern. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared in dependencies; SDK re-export pattern. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Declared in dependencies; used in openapi/swagger middleware exports. | ai | |
| phantom-deps | phantom-dep:js-cookie | AI (phantom-deps): Declared in dependencies; SDK utility pattern. | ai | |
| phantom-deps | phantom-dep:openapi-types | AI (phantom-deps): Declared in dependencies; type-only usage common in compiled TS packages. | ai | |
| phantom-deps | phantom-dep:swagger-jsdoc | AI (phantom-deps): Declared in dependencies; used in openapi export. | ai | |
| phantom-deps | phantom-dep:openapi-enforcer | AI (phantom-deps): Declared in dependencies; used in openapi validation. | ai | |
| phantom-deps | phantom-dep:@blocklet/constant | AI (phantom-deps): Same org scope; declared in dependencies, stable false positive. | ai | |
| phantom-deps | phantom-dep:swagger-ui-express | AI (phantom-deps): Declared in dependencies; used in openapi/swagger middleware. | ai | |
| phantom-deps | phantom-dep:@types/swagger-jsdoc | AI (phantom-deps): Type-only package; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/swagger-ui-express | AI (phantom-deps): Type-only package; framework-scoped, stable false positive. | ai |
Versions (showing 100 of 431)
| Version | Deps | Published |
|---|---|---|
| 0.4.109 | 17 / 5 | |
| 0.4.108 | 17 / 5 | |
| 0.4.107 | 17 / 5 | |
| 0.4.106 | 17 / 5 | |
| 0.4.105 | 17 / 5 | |
| 0.4.104 | 17 / 5 | |
| 0.4.103 | 17 / 5 | |
| 0.4.102 | 17 / 5 | |
| 0.4.101 | 17 / 5 | |
| 0.4.100 | 17 / 5 | |
| 0.4.99 | 17 / 5 | |
| 0.4.98 | 17 / 5 | |
| 0.4.97 | 17 / 5 | |
| 0.4.96 | 17 / 5 | |
| 0.4.95 | 17 / 5 | |
| 0.4.94 | 17 / 5 | |
| 0.4.93 | 17 / 5 | |
| 0.4.92 | 17 / 5 | |
| 0.4.91 | 17 / 5 | |
| 0.4.90 | 17 / 5 | |
| 0.4.89 | 17 / 5 | |
| 0.4.88 | 17 / 5 | |
| 0.4.87 | 17 / 5 | |
| 0.4.86 | 17 / 5 | |
| 0.4.85 | 17 / 5 | |
| 0.4.84 | 17 / 5 | |
| 0.4.83 | 17 / 5 | |
| 0.4.82 | 17 / 5 | |
| 0.4.81 | 17 / 5 | |
| 0.4.80 | 17 / 5 | |
| 0.4.79 | 17 / 5 | |
| 0.4.78 | 17 / 5 | |
| 0.4.77 | 17 / 5 | |
| 0.4.76 | 17 / 5 | |
| 0.4.75 | 17 / 5 | |
| 0.4.74 | 17 / 5 | |
| 0.4.73 | 17 / 5 | |
| 0.4.72 | 17 / 5 | |
| 0.4.71 | 17 / 5 | |
| 0.4.70 | 17 / 5 | |
| 0.4.69 | 17 / 5 | |
| 0.4.68 | 17 / 5 | |
| 0.4.67 | 17 / 5 | |
| 0.4.66 | 17 / 5 | |
| 0.4.65 | 17 / 5 | |
| 0.4.64 | 17 / 5 | |
| 0.4.63 | 17 / 5 | |
| 0.4.62 | 17 / 5 | |
| 0.4.61 | 17 / 5 | |
| 0.4.60 | 17 / 5 | |
| 0.4.59 | 17 / 5 | |
| 0.4.58 | 17 / 5 | |
| 0.4.57 | 17 / 5 | |
| 0.4.56 | 16 / 5 | |
| 0.4.55 | 16 / 5 | |
| 0.4.54 | 16 / 5 | |
| 0.4.53 | 16 / 5 | |
| 0.4.52 | 16 / 5 | |
| 0.4.51 | 16 / 5 | |
| 0.4.50 | 16 / 5 | |
| 0.4.49 | 16 / 5 | |
| 0.4.48 | 16 / 5 | |
| 0.4.47 | 16 / 5 | |
| 0.4.46 | 16 / 5 | |
| 0.4.45 | 16 / 5 | |
| 0.4.44 | 16 / 5 | |
| 0.4.43 | 16 / 5 | |
| 0.4.42 | 16 / 5 | |
| 0.4.41 | 16 / 5 | |
| 0.4.40 | 16 / 5 | |
| 0.4.39 | 16 / 5 | |
| 0.4.38 | 16 / 5 | |
| 0.4.37 | 16 / 5 | |
| 0.4.36 | 16 / 5 | |
| 0.4.35 | 16 / 5 | |
| 0.4.34 | 16 / 5 | |
| 0.4.33 | 16 / 5 | |
| 0.4.32 | 16 / 5 | |
| 0.4.31 | 16 / 5 | |
| 0.4.30 | 16 / 5 | |
| 0.4.29 | 16 / 5 | |
| 0.4.28 | 16 / 5 | |
| 0.4.27 | 16 / 5 | |
| 0.4.26 | 16 / 5 | |
| 0.4.25 | 16 / 5 | |
| 0.4.24 | 16 / 5 | |
| 0.4.23 | 16 / 5 | |
| 0.4.22 | 16 / 5 | |
| 0.4.21 | 16 / 5 | |
| 0.4.20 | 16 / 5 | |
| 0.4.19 | 16 / 5 | |
| 0.4.18 | 16 / 5 | |
| 0.4.17 | 16 / 5 | |
| 0.4.16 | 16 / 5 | |
| 0.4.15 | 16 / 5 | |
| 0.4.14 | 16 / 5 | |
| 0.4.13 | 16 / 5 | |
| 0.4.12 | 16 / 5 | |
| 0.4.11 | 16 / 5 | |
| 0.4.10 | 16 / 5 |
v0.4.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.