@sitecore-jss/sitecore-jss-angular
This module is provided as a part of Sitecore JavaScript Rendering SDK (JSS). It contains Angular integration components and services for JSS.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm2022/components/base-field.directive.mjs | AI (source-diff): Long-line ng-packagr build output, not obfuscation; source is readable. | ai | |
| source-diff | obfuscated-file:dist/esm2022/components/editing-scripts.component.mjs | AI (source-diff): Long-line ng-packagr build output, not obfuscation; source is readable. | ai | |
| source-diff | obfuscated-file:dist/esm2022/components/form.component.mjs | AI (source-diff): Long-line ng-packagr build output, not obfuscation; source is readable. | ai | |
| provenance | publisher-changed | AI (provenance): sc_illiakovalenko is an established Sitecore publisher account with 7 approved packages; consistent with org-internal maintainer transition. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 22.12.4 | 1 / 32 | |
| 22.12.3 | 1 / 32 | |
| 22.12.1 | 1 / 32 | |
| 22.12.0 | 1 / 32 | |
| 22.11.0 | 1 / 29 | |
| 22.10.0 | 1 / 29 | |
| 22.9.1 | 1 / 29 | |
| 22.9.0 | 1 / 29 | |
| 22.8.0 | 1 / 29 | |
| 22.7.0 | 1 / 29 | |
| 22.6.0 | 1 / 29 | |
| 22.5.5 | 1 / 30 | |
| 22.5.4 | 1 / 30 | |
| 22.5.3 | 1 / 30 | |
| 22.5.2 | 1 / 30 | |
| 22.5.1 | 1 / 30 | |
| 22.5.0 | 1 / 30 | |
| 22.4.1 | 1 / 30 | |
| 22.4.0 | 1 / 30 | |
| 22.3.1 | 1 / 30 | |
| 22.3.0 | 1 / 29 | |
| 22.2.1 | 1 / 29 | |
| 22.2.0 | 1 / 29 | |
| 22.1.4 | 1 / 29 | |
| 22.1.3 | 1 / 29 | |
| 22.1.2 | 1 / 29 | |
| 22.1.1 | 1 / 29 | |
| 22.1.0 | 1 / 29 | |
| 21.11.0 | 1 / 32 | |
| 21.10.1 | 1 / 29 |
v22.12.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (sc-artemalexeyenko) on 2026-07-14, but sc_illiakovalenko 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.
v22.12.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sc-artemalexeyenko) than the most recent previously approved version (sc_illiakovalenko) on 2026-05-04, but sc-artemalexeyenko 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.
v22.5.5
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-04-25, but sitecorecorporation 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.
v22.5.4
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-03-21, but sitecorecorporation 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.
v22.5.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-03-19, but sitecorecorporation 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.
v22.5.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-03-03, but sitecorecorporation 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.
v22.5.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-02-27, but sitecorecorporation 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.
v22.5.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-02-11, but sitecorecorporation 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.
v22.4.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-01-28, but sitecorecorporation 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.
v22.4.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-01-23, but sitecorecorporation 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.
v22.3.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2024-12-09, but sitecorecorporation 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.
v22.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (sc-yavorkrastev) on 2024-11-24, but sc_illiakovalenko 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.
v22.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (sc-yavorkrastev) on 2024-11-13, but sc_illiakovalenko 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.
v22.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sc-yavorkrastev) than the most recent previously approved version (sc_illiakovalenko) on 2024-10-21, but sc-yavorkrastev 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.
v22.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (apathania) on 2024-09-02, but sc_illiakovalenko 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.
v22.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.