@progress/sitefinity-nextjs-sdk

Provides OOB widgets developed using the Next.js framework, which includes an abstraction layer for Sitefinity communication. Additionally, it offers an expanded API, typings, and tools for further development and integration.

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

progress

Keywords

sitefinityrendererwidgetreactnextjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:widgets/answer/answer.view.js	AI (source-diff): File is readable JSX/React code; long lines are inline config objects, not obfuscation. Stable false positive for this SDK package.	ai	2026/05/20
provenance	no-provenance	AI (provenance): Progress/Sitefinity packages consistently publish without Sigstore provenance; stable pattern across all versions.	ai	2026/05/16
license	uncommon-license:EULA.md	AI (license): Progress uses a custom EULA.md license consistently across their SDK packages; not a security concern.	ai	2026/05/16

Versions (showing 32 of 32)

Version	Deps	Published
15.4.8631	1 / 0	2026-05-26
15.4.8630	1 / 0	2026-05-11
15.4.8629	1 / 0	2026-04-30
15.4.8628	1 / 0	2026-04-01
15.4.8627	1 / 0	2026-03-24
15.4.8626	1 / 0	2026-02-26
15.4.8625	1 / 0	2026-02-11
15.4.8624	1 / 0	2026-01-27
15.4.8623	1 / 0	2025-12-15
15.4.8622	1 / 0	2025-12-05
15.4.8621	1 / 0	2025-11-10
15.4.8600	1 / 0	2025-11-05
15.3.8530	1 / 0	2025-12-15
15.3.8529	1 / 0	2025-12-05
15.3.8528	1 / 0	2025-11-04
15.3.8527	1 / 0	2025-10-28
15.3.8526	1 / 0	2025-10-14
15.3.8525	1 / 0	2025-10-13
15.3.8524	1 / 0	2025-08-26
15.3.8523	1 / 0	2025-07-09
15.3.8522	1 / 0	2025-05-30
15.3.8521	1 / 0	2025-05-21
15.2.8439	1 / 0	2025-12-15
15.2.8438	1 / 0	2025-11-24
15.2.8437	1 / 0	2025-11-11
15.2.8436	1 / 0	2025-10-28
15.2.8435	1 / 0	2025-08-28
15.2.8434	1 / 0	2025-08-28
15.2.8433	1 / 0	2025-06-30
15.2.8432	1 / 0	2025-06-02
15.2.8431	1 / 0	2025-05-15
15.2.8430	1 / 0	2025-05-15

v15.4.8631

1 finding

INFO No provenance attestation provenance

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

v15.4.8630

1 finding

INFO No provenance attestation provenance

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

v15.4.8629

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.

v15.4.8628

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.

v15.4.8627

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.

v15.4.8626

2 findings

HIGH New obfuscated file: widgets/answer/answer.view.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.

INFO No provenance attestation provenance

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

v15.4.8625

1 finding

INFO No provenance attestation provenance

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

v15.4.8624

1 finding

INFO No provenance attestation provenance

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

v15.4.8623

1 finding

INFO No provenance attestation provenance

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

v15.4.8622

1 finding

INFO No provenance attestation provenance

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

v15.4.8621

1 finding

INFO No provenance attestation provenance

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

v15.4.8600

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.

v15.3.8530

1 finding

INFO No provenance attestation provenance

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

v15.3.8529

1 finding

INFO No provenance attestation provenance

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

v15.3.8528

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.

v15.3.8527

1 finding

LOW No provenance attestation provenance

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

v15.3.8526

1 finding

LOW No provenance attestation provenance

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

v15.3.8525

1 finding

LOW No provenance attestation provenance

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

v15.3.8524

1 finding

LOW No provenance attestation provenance

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

v15.3.8523

1 finding

LOW No provenance attestation provenance

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

v15.3.8522

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.

v15.3.8521

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.

v15.2.8439

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.

v15.2.8438

1 finding

INFO No provenance attestation provenance

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

v15.2.8437

1 finding

INFO No provenance attestation provenance

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

v15.2.8436

1 finding

LOW No provenance attestation provenance

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

v15.2.8435

1 finding

LOW No provenance attestation provenance

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

v15.2.8434

1 finding

LOW No provenance attestation provenance

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

v15.2.8433

1 finding

LOW No provenance attestation provenance

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

v15.2.8432

1 finding

LOW No provenance attestation provenance

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

v15.2.8431

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.

v15.2.8430

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.