@jtl-software/cloud-app-template-frontend-react
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All added deps (react, graphql, graphql-request, react-dom, platform-ui-react, cloud-apps-core) are expected for a React+GraphQL frontend template. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal JTL template package; sparse metadata is expected for early-stage org tooling, not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a declared runtime dep used via graphql-request/config; not a true phantom. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.0.16 | 6 / 14 | |
| 0.0.15 | 6 / 14 | |
| 0.0.14 | 6 / 14 | |
| 0.0.13 | 6 / 14 | |
| 0.0.12 | 6 / 14 | |
| 0.0.11 | 6 / 14 | |
| 0.0.10 | 6 / 14 | |
| 0.0.9 | 6 / 14 | |
| 0.0.8 | 6 / 14 | |
| 0.0.7 | 4 / 14 | |
| 0.0.6 | 4 / 14 | |
| 0.0.5 | 4 / 14 | |
| 0.0.4 | 4 / 14 | |
| 0.0.3 | 4 / 14 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
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 (sebastian-wemogy) than the most recent previously approved version (erpdev) on 2026-05-22, but sebastian-wemogy 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.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.