@iblai/iblai-js
Unified JavaScript SDK for IBL.ai — re-exports data-layer, web-containers, and web-utils under a single package
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/web-containers/source/next/index.esm.js | AI (source-diff): Encoded string is html2canvas Base64 alphabet table — benign bundled dependency, not obfuscated malware. | ai | |
| provenance | missing-githead | AI (provenance): Provenance gap only; no other risk signals present and package content is consistent with prior approved versions. | ai | |
| provenance | no-provenance | AI (provenance): Org-published SDK; no provenance is consistent across all versions and poses no direct security risk. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is a legitimate runtime dep used by the ibl-mcp-server bin entry point, not a phantom dependency. | ai |
Versions (showing 78 of 178)
| Version | Deps | Published |
|---|---|---|
| 1.10.3 | 7 / 11 | |
| 1.10.2 | 7 / 11 | |
| 1.10.0 | 7 / 11 | |
| 1.9.11 | 7 / 11 | |
| 1.9.10 | 7 / 11 | |
| 1.9.9 | 7 / 11 | |
| 1.9.8 | 7 / 11 | |
| 1.9.7 | 7 / 11 | |
| 1.9.6 | 7 / 11 | |
| 1.9.5 | 7 / 11 | |
| 1.9.4 | 7 / 11 | |
| 1.9.3 | 7 / 11 | |
| 1.9.2 | 7 / 11 | |
| 1.9.1 | 7 / 11 | |
| 1.9.0 | 7 / 11 | |
| 1.8.8 | 7 / 11 | |
| 1.8.7 | 7 / 11 | |
| 1.8.5 | 7 / 11 | |
| 1.8.4 | 7 / 11 | |
| 1.8.3 | 7 / 11 | |
| 1.8.2 | 7 / 11 | |
| 1.8.0 | 7 / 11 | |
| 1.7.0 | 7 / 11 | |
| 1.6.2 | 7 / 11 | |
| 1.6.1 | 7 / 11 | |
| 1.6.0 | 7 / 11 | |
| 1.5.4 | 7 / 11 | |
| 1.5.3 | 7 / 11 | |
| 1.5.2 | 7 / 11 | |
| 1.5.1 | 7 / 11 | |
| 1.5.0 | 7 / 11 | |
| 1.4.18 | 7 / 11 | |
| 1.1.6 | 7 / 11 | |
| 1.1.5 | 7 / 11 | |
| 1.1.4 | 7 / 11 | |
| 1.1.3 | 7 / 11 | |
| 1.1.2 | 7 / 11 | |
| 1.1.1 | 7 / 11 | |
| 1.1.0 | 7 / 11 | |
| 1.0.39 | 7 / 11 | |
| 1.0.38 | 7 / 11 | |
| 1.0.37 | 7 / 11 | |
| 1.0.36 | 7 / 11 | |
| 1.0.35 | 7 / 11 | |
| 1.0.34 | 7 / 11 | |
| 1.0.33 | 7 / 11 | |
| 1.0.32 | 7 / 11 | |
| 1.0.31 | 7 / 11 | |
| 1.0.30 | 7 / 11 | |
| 1.0.29 | 7 / 11 | |
| 1.0.28 | 7 / 11 | |
| 1.0.27 | 7 / 11 | |
| 1.0.26 | 6 / 11 | |
| 1.0.24 | 6 / 11 | |
| 1.0.23 | 6 / 11 | |
| 1.0.22 | 6 / 11 | |
| 1.0.21 | 6 / 11 | |
| 1.0.20 | 3 / 13 | |
| 1.0.19 | 3 / 13 | |
| 1.0.18 | 3 / 13 | |
| 1.0.17 | 3 / 8 | |
| 1.0.16 | 3 / 8 | |
| 1.0.15 | 3 / 7 | |
| 1.0.14 | 3 / 7 | |
| 1.0.13 | 3 / 7 | |
| 1.0.12 | 3 / 7 | |
| 1.0.11 | 3 / 7 | |
| 1.0.10 | 3 / 7 | |
| 1.0.9 | 3 / 7 | |
| 1.0.8 | 3 / 7 | |
| 1.0.7 | 3 / 7 | |
| 1.0.6 | 3 / 7 | |
| 1.0.5 | 3 / 7 | |
| 1.0.4 | 3 / 7 | |
| 1.0.3 | 3 / 7 | |
| 1.0.2 | 3 / 7 | |
| 1.0.1 | 3 / 7 | |
| 1.0.0 | 3 / 12 |
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.