← Home

@iblai/web-containers

ibl web containers

5
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

iblbnsoniconradibleducationgillismiguelamigotbeckham45babatundeiblgipsbrian

Keywords

web

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/next/index.esm.js AI (source-diff): Long base64 string is html2canvas's Unicode lookup table (MIT, Niklas von Hertzen) — stable false positive for this package. ai
source-diff encoded-string-file:dist/next/index.js AI (source-diff): Same html2canvas Unicode lookup table in CJS build — stable false positive for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.8.3 62 / 44
1.6.14 62 / 44
1.6.12 55 / 44
1.4.0 54 / 44
1.3.16 54 / 43

v1.8.3

3 findings
HIGH Long encoded string in modified file: dist/next/index.esm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/next/index.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.14

3 findings
HIGH Long encoded string in modified file: dist/next/index.esm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/next/index.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.