@web-utils/integrations
Web Integrations
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jspdf | AI (phantom-deps): Subpath export ./jspdf.js imports jspdf directly; top-level barrel scan misses it. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Subpath export ./uuid.js imports uuid directly; top-level barrel scan misses it. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Subpath export ./dayjs.js imports dayjs directly; top-level barrel scan misses it. | ai | |
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): Subpath export ./resize.js imports this directly; top-level barrel scan misses it. | ai | |
| phantom-deps | phantom-dep:jsencrypt | AI (phantom-deps): Subpath export ./encrypt.js imports jsencrypt directly; top-level barrel scan misses it. | ai | |
| phantom-deps | phantom-dep:@web-utils/core | AI (phantom-deps): Same-org dep used in subpath modules; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 73 versions; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 11 / 0 | |
| 6.0.1 | 11 / 0 | |
| 5.0.4 | 11 / 0 | |
| 5.0.3 | 11 / 0 | |
| 5.0.2 | 11 / 0 | |
| 5.0.1 | 11 / 0 | |
| 5.0.0 | 10 / 0 |
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.