@iblai/web-utils
IBL Web Utils
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/web-utils/src/features/subscription/slice.d.ts | AI (source-diff): Long lines are RTK ActionCreator union type generics in a .d.ts file, not obfuscation. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): Build tool used in rollup config; expected pattern for build dependencies. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-copy | AI (phantom-deps): Build plugin used in rollup config; expected pattern for build dependencies. | ai | |
| phantom-deps | phantom-dep:jwt-decode | AI (phantom-deps): Legitimately imported in source; phantom-dep is a false positive. | ai |
Versions (showing 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 9 / 29 | |
| 1.11.8 | 9 / 29 | |
| 1.11.7 | 9 / 29 | |
| 1.11.6 | 9 / 29 | |
| 1.11.5 | 9 / 29 | |
| 1.11.4 | 9 / 29 | |
| 1.11.3 | 9 / 29 | |
| 1.11.2 | 9 / 29 | |
| 1.11.0 | 9 / 29 | |
| 1.10.12 | 9 / 29 | |
| 1.10.11 | 9 / 29 | |
| 1.10.10 | 9 / 29 | |
| 1.10.9 | 9 / 29 | |
| 1.10.8 | 9 / 29 | |
| 1.10.7 | 9 / 29 | |
| 1.10.6 | 9 / 29 | |
| 1.10.5 | 9 / 29 | |
| 1.10.4 | 9 / 29 | |
| 1.10.3 | 9 / 29 | |
| 1.10.2 | 9 / 29 | |
| 1.10.1 | 9 / 29 | |
| 1.10.0 | 9 / 29 | |
| 1.9.2 | 9 / 29 | |
| 1.9.1 | 9 / 29 | |
| 1.9.0 | 9 / 29 | |
| 1.8.1 | 9 / 29 | |
| 1.8.0 | 9 / 29 | |
| 1.7.3 | 9 / 29 | |
| 1.7.2 | 9 / 29 | |
| 1.7.1 | 9 / 29 | |
| 1.7.0 | 9 / 29 | |
| 1.6.10 | 9 / 29 | |
| 1.6.9 | 9 / 29 | |
| 1.6.8 | 8 / 29 | |
| 1.6.7 | 8 / 29 | |
| 1.6.6 | 8 / 29 | |
| 1.6.5 | 8 / 29 | |
| 1.6.4 | 8 / 29 | |
| 1.6.3 | 8 / 29 | |
| 1.6.2 | 8 / 29 | |
| 1.6.1 | 8 / 29 | |
| 1.6.0 | 8 / 29 | |
| 1.5.0 | 8 / 29 | |
| 1.4.1 | 8 / 29 | |
| 1.4.0 | 8 / 29 | |
| 1.3.2 | 8 / 29 | |
| 1.3.1 | 8 / 29 | |
| 1.3.0 | 8 / 29 | |
| 1.2.13 | 8 / 29 | |
| 1.2.12 | 8 / 29 | |
| 1.2.11 | 8 / 29 | |
| 1.2.10 | 8 / 29 | |
| 1.2.9 | 8 / 29 | |
| 1.2.8 | 8 / 29 | |
| 1.2.7 | 8 / 29 | |
| 1.2.6 | 8 / 29 | |
| 1.2.5 | 8 / 29 | |
| 1.2.4 | 8 / 29 | |
| 1.2.3 | 8 / 29 | |
| 1.2.2 | 8 / 29 | |
| 1.2.1 | 8 / 29 | |
| 1.2.0 | 8 / 29 | |
| 1.1.18 | 8 / 29 | |
| 1.1.17 | 8 / 29 | |
| 1.1.16 | 8 / 29 | |
| 1.1.15 | 8 / 29 | |
| 1.1.14 | 8 / 29 | |
| 1.1.13 | 8 / 29 | |
| 1.1.12 | 8 / 29 | |
| 1.1.11 | 8 / 29 | |
| 1.1.10 | 8 / 29 | |
| 1.1.9 | 8 / 29 | |
| 1.1.8 | 8 / 29 | |
| 1.1.7 | 8 / 29 | |
| 1.1.6 | 8 / 29 | |
| 1.1.5 | 8 / 29 | |
| 1.1.4 | 8 / 29 | |
| 1.1.3 | 8 / 29 | |
| 1.1.2 | 8 / 27 | |
| 1.1.1 | 9 / 27 | |
| 1.0.0 | 9 / 27 | |
| 0.3.0 | 9 / 27 | |
| 0.2.1 | 9 / 27 |
v1.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.