@iblai/data-layer
ibl.ai data layer
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency used transitively; phantom-dep heuristic fires but it's a legitimate dep. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-copy | AI (phantom-deps): rollup-plugin-copy referenced in build config; phantom-dep heuristic fires but usage is legitimate. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.5.10 | 3 / 26 | |
| 1.5.7 | 3 / 26 | |
| 1.5.6 | 3 / 26 | |
| 1.5.5 | 3 / 26 | |
| 1.5.4 | 3 / 26 | |
| 1.5.3 | 3 / 26 | |
| 1.5.1 | 3 / 26 | |
| 1.5.0 | 3 / 26 | |
| 1.4.4 | 3 / 26 | |
| 1.4.3 | 3 / 26 | |
| 1.4.0 | 3 / 26 | |
| 1.3.11 | 3 / 26 | |
| 1.3.10 | 3 / 26 | |
| 1.3.9 | 3 / 26 | |
| 1.3.8 | 3 / 26 | |
| 1.3.7 | 3 / 26 | |
| 1.3.5 | 3 / 26 | |
| 1.3.2 | 3 / 26 | |
| 1.3.1 | 3 / 26 | |
| 1.2.9 | 3 / 26 | |
| 1.2.8 | 3 / 26 | |
| 1.2.7 | 3 / 26 | |
| 1.2.6 | 3 / 26 | |
| 1.2.5 | 3 / 26 | |
| 1.2.4 | 3 / 26 |
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.