@sitecore-jss/sitecore-jss-dev-tools
Utilities to assist in the development and deployment of Sitecore JSS apps.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): Config-referenced CLI tool; stable for dev-tool packages. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Config-referenced test runner; stable for TypeScript dev-tools. | ai | |
| phantom-deps | phantom-dep:module-alias | AI (phantom-deps): Config-referenced module loader; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/parser | AI (phantom-deps): Framework-scoped package loaded by convention; stable pattern. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 22.12.1 | 21 / 26 | |
| 22.10.0 | 21 / 26 | |
| 22.9.1 | 21 / 26 | |
| 22.9.0 | 21 / 26 | |
| 22.8.0 | 21 / 28 | |
| 22.7.0 | 21 / 28 | |
| 22.6.0 | 21 / 28 | |
| 21.11.0 | 22 / 27 | |
| 21.10.1 | 22 / 27 |
v22.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.