← Home

@microsoft/sp-listview-extensibility

SharePoint Framework developer support for customizing the list view

8
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

microsoft1esmicrosoft-oss-releasesodspnpm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/sp-listview-extensibility_none_48806aea6837984049e7.js AI (source-diff): Standard webpack bundle output, not true obfuscation; consistent with SPFx build tooling. ai
publish-pattern new-deps-added AI (publish-pattern): @swc/helpers is a well-known build helper library, benign addition. ai
source-diff obfuscated-file:dist/sp-listview-extensibility_none_32211638f8dca1a8efaa.js AI (source-diff): Standard webpack bundle for Microsoft SPFx package; content is readable SPFx extension code, not malicious obfuscation. ai
bogus-package bogus-package AI (bogus-package): SDK sub-package; sparse README/keywords is normal for Microsoft SPFx component libraries. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): Known implicit transitive dep for SWC-compiled output; stable pattern for this package family. ai

Versions (showing 8 of 8)

Version Deps Published
1.23.0 6 / 4
1.22.2 6 / 4
1.22.1 6 / 4
1.22.0 6 / 4
1.21.1 6 / 4
1.21.0 6 / 4
1.20.0 5 / 4
1.19.0 5 / 4

v1.21.0

3 findings
HIGH New obfuscated file: dist/sp-listview-extensibility_none_48806aea6837984049e7.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.

INFO Publisher changed: odspnpm → microsoft1es (on 2025-04-23, known maintainer) provenance

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2025-04-23, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.20.0

3 findings
HIGH New obfuscated file: dist/sp-listview-extensibility_none_12c091b9cf01a2d676da.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.

INFO Publisher changed: odspnpm → microsoft1es (on 2024-09-26, known maintainer) provenance

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2024-09-26, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.19.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.