← Home

@microsoft/sp-image-helper

npm Homepage

Image helper APIs for the Sharepoint Framework.

5
Versions
https://aka.ms/spfx/license
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

microsoft1esmicrosoft-oss-releasesodspnpm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/sp-image-helper_none_102a5490b69a1a7f9ae1.js AI (source-diff): Standard SPFx webpack bundle; minified but not obfuscated — readable Microsoft-internal symbols and hostnames visible in sample. ai
maintainer-change maintainer-added AI (maintainer-change): microsoft-oss-releases is a known Microsoft release automation account; consistent with org publishing practices. ai
bogus-package bogus-package AI (bogus-package): Microsoft SPFx SDK component; sparse README and no keywords are expected for internal framework packages. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): Known implicit runtime dep for SWC-compiled output; stable pattern for this package family. ai
phantom-deps phantom-dep:@microsoft/sp-http-base AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive here. ai

Versions (showing 5 of 5)

Version Deps Published
1.23.0 8 / 12
1.22.2 8 / 13
1.22.1 8 / 13
1.22.0 8 / 13
1.21.1 8 / 13

v1.23.0

2 findings
HIGH New obfuscated file: dist/sp-image-helper_none_102a5490b69a1a7f9ae1.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.22.1

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.

v1.22.0

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.

v1.21.1

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.