@muil/templates-renderer
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established package with 41 versions; missing metadata is cosmetic, not indicative of malicious intent. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a transitive peer dep of @nestjs/common; phantom detection is a false positive here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Template renderer loads user React components dynamically by design; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known NestJS implicit peer dep; declared in dependencies, not a phantom. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 7 / 2 | |
| 3.1.1 | 7 / 2 | |
| 3.0.0 | 7 / 2 | |
| 2.2.6 | 8 / 3 | |
| 2.2.5 | 8 / 3 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.