@jtl-software/cloud-app-template-backend-dotnet
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs conditional dotnet restore on a template placeholder path; no network fetch or arbitrary code execution. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 0 / 0 | |
| 0.0.8 | 0 / 0 | |
| 0.0.7 | 0 / 0 | |
| 0.0.5 | 0 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.0.9
2 findingsScript: node -e "var p='{{APP_NAME_PASCAL}}.Api';require('fs').existsSync(p)&&require('child_process').execSync('dotnet restore '+p,{stdio:'inherit'})"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
2 findingsScript: node -e "var p='{{APP_NAME_PASCAL}}.Api';require('fs').existsSync(p)&&require('child_process').execSync('dotnet restore '+p,{stdio:'inherit'})"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
2 findingsScript: node -e "var p='{{APP_NAME_PASCAL}}.Api';require('fs').existsSync(p)&&require('child_process').execSync('dotnet restore '+p,{stdio:'inherit'})"
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsScript: if [ -d '{{APP_NAME_PASCAL}}.Api' ]; then dotnet restore {{APP_NAME_PASCAL}}.Api; fi
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.