@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.
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
Keywords
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 | |
| provenance | no-provenance | AI (provenance): Progress/Sitefinity packages consistently publish without Sigstore provenance; stable pattern across all versions. | ai | |
| license | uncommon-license:EULA.md | AI (license): Progress uses a custom EULA.md license consistently across their SDK packages; not a security concern. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 15.4.8632 | 1 / 0 | |
| 15.4.8631 | 1 / 0 | |
| 15.4.8630 | 1 / 0 | |
| 15.4.8629 | 1 / 0 | |
| 15.4.8628 | 1 / 0 | |
| 15.4.8627 | 1 / 0 | |
| 15.4.8626 | 1 / 0 | |
| 15.4.8625 | 1 / 0 | |
| 15.4.8624 | 1 / 0 | |
| 15.4.8623 | 1 / 0 | |
| 15.4.8622 | 1 / 0 | |
| 15.4.8621 | 1 / 0 | |
| 15.4.8600 | 1 / 0 | |
| 15.3.8530 | 1 / 0 | |
| 15.3.8529 | 1 / 0 | |
| 15.3.8528 | 1 / 0 | |
| 15.3.8527 | 1 / 0 | |
| 15.3.8526 | 1 / 0 | |
| 15.3.8525 | 1 / 0 | |
| 15.3.8524 | 1 / 0 | |
| 15.3.8523 | 1 / 0 | |
| 15.3.8522 | 1 / 0 | |
| 15.3.8521 | 1 / 0 | |
| 15.3.8500 | 1 / 0 | |
| 15.2.8439 | 1 / 0 | |
| 15.2.8438 | 1 / 0 | |
| 15.2.8437 | 1 / 0 | |
| 15.2.8436 | 1 / 0 | |
| 15.2.8435 | 1 / 0 | |
| 15.2.8434 | 1 / 0 | |
| 15.2.8433 | 1 / 0 | |
| 15.2.8432 | 1 / 0 | |
| 15.2.8431 | 1 / 0 | |
| 15.2.8430 | 1 / 0 | |
| 15.2.8429 | 1 / 0 | |
| 15.2.8428 | 1 / 0 | |
| 15.2.8427 | 1 / 0 | |
| 15.2.8426 | 1 / 0 | |
| 15.2.8425 | 1 / 0 | |
| 15.2.8424 | 1 / 0 | |
| 15.2.8423 | 1 / 0 | |
| 15.2.8422 | 1 / 0 | |
| 15.2.8421 | 1 / 0 | |
| 15.2.8400 | 1 / 0 | |
| 15.1.8327 | 1 / 0 | |
| 15.1.8326 | 1 / 0 |
v15.4.8632
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.8500
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8429
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8428
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8427
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8426
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8425
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8424
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8423
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8422
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8421
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.8400
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.8327
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.8326
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.