@adobe/helix-shared-async No license 2 versions

@adobe/helix-shared-async

npm Repository Homepage

Versions

—

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

djaeggiadobehallsfullcolorcodermarbectripodgarthdblazdadobe-adminpatrickfultontrieloffshazronkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergkorrarofekptdobe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Adobe org team rotation; adobe-admin publisher has strong track record across many packages.	ai	2026/05/17
maintainer-change	maintainer-removed	AI (maintainer-change): Part of normal Adobe org team management, not indicative of takeover.	ai	2026/05/17
bogus-package	bogus-package	AI (bogus-package): Legitimate Adobe Helix shared utility; sparse README/no-deps is expected for a small utility module.	ai	2026/05/17

Versions (showing 2 of 2)

Version	Deps	Published
2.0.3	0 / 0	2025-07-14
2.0.2	0 / 1	2024-04-17

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.