@decaf-ts/for-nest
NestJS decaf integration
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/for-nest.js | AI (source-diff): dist/ is standard bundled minified output for this package; no malicious patterns in sample. | ai | |
| source-diff | obfuscated-file:lib/esm/factory/exceptions/ValidationExceptionFilter.js | AI (source-diff): ESM counterpart; same inline sourcemap pattern, readable code. | ai | |
| source-diff | obfuscated-file:lib/esm/factory/openapi/SwaggerCustomUI.js | AI (source-diff): ESM counterpart; same inline sourcemap pattern, readable code. | ai | |
| source-diff | obfuscated-file:lib/factory/exceptions/AuthorizationExceptionFilter.cjs | AI (source-diff): Inline sourcemap causes long lines; code is readable NestJS exception filter. | ai | |
| source-diff | obfuscated-file:lib/factory/exceptions/GlobalExceptionFilter.cjs | AI (source-diff): Inline sourcemap causes long lines; code is readable NestJS exception filter. | ai | |
| source-diff | obfuscated-file:lib/factory/NestBootstraper.cjs | AI (source-diff): Inline sourcemap causes long lines; code is readable NestJS bootstrapper. | ai | |
| source-diff | obfuscated-file:lib/factory/openapi/SwaggerBuilder.cjs | AI (source-diff): Inline sourcemap causes long lines; code is readable Swagger builder. | ai | |
| source-diff | obfuscated-file:lib/factory/openapi/SwaggerCustomUI.cjs | AI (source-diff): Inline sourcemap causes long lines; code is readable Swagger UI customization. | ai | |
| source-diff | obfuscated-file:lib/factory/exceptions/ValidationExceptionFilter.cjs | AI (source-diff): Inline sourcemap causes long lines; code is readable NestJS validation filter. | ai | |
| source-diff | obfuscated-file:lib/esm/factory/exceptions/AuthorizationExceptionFilter.js | AI (source-diff): ESM counterpart; same inline sourcemap pattern, readable code. | ai | |
| source-diff | obfuscated-file:lib/esm/factory/exceptions/GlobalExceptionFilter.js | AI (source-diff): ESM counterpart; same inline sourcemap pattern, readable code. | ai | |
| source-diff | obfuscated-file:lib/esm/factory/openapi/SwaggerBuilder.js | AI (source-diff): ESM counterpart; same inline sourcemap pattern, readable code. | ai | |
| source-diff | obfuscated-file:lib/esm/factory/NestBootstraper.js | AI (source-diff): ESM counterpart; same inline sourcemap pattern, readable code. | ai | |
| source-diff | obfuscated-file:lib/esm/model-module.js | AI (source-diff): Standard ESM TypeScript compiler output with __decorate/__metadata boilerplate. | ai | |
| source-diff | obfuscated-file:lib/esm/decorators/ApiProperty.js | AI (source-diff): Standard ESM TypeScript compiler output; readable NestJS/Swagger decorator code. | ai | |
| source-diff | obfuscated-file:lib/esm/decoration.js | AI (source-diff): Standard ESM TypeScript compiler output; readable NestJS integration code. | ai | |
| source-diff | obfuscated-file:lib/esm/decorators/helpers.js | AI (source-diff): Standard ESM TypeScript compiler output; readable decorator helper code. | ai | |
| source-diff | obfuscated-file:lib/decorators/ApiProperty.cjs | AI (source-diff): Standard TypeScript compiler output; long lines from bundled decorator logic, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/decoration.cjs | AI (source-diff): Standard TypeScript compiler output; readable NestJS integration code. | ai | |
| source-diff | obfuscated-file:lib/decorators/helpers.cjs | AI (source-diff): Standard TypeScript compiler output; readable decorator helper code. | ai | |
| source-diff | obfuscated-file:lib/model-module.cjs | AI (source-diff): Standard TypeScript compiler output with __decorate/__metadata boilerplate. | ai | |
| dependencies | unvetted-dep:@decaf-ts/logging | AI (dependencies): Same org (@decaf-ts) dependency; consistent with the rest of the package's dependency graph. | ai | |
| phantom-deps | phantom-dep:@decaf-ts/transactional-decorators | AI (phantom-deps): Same org scope; declared as dep, likely re-exported transitively rather than directly imported. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in CLI module loading user-specified NestJS app modules by path — expected pattern for this tooling. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.3.14 | 9 / 17 | |
| 0.3.13 | 8 / 17 | |
| 0.3.12 | 8 / 17 | |
| 0.3.11 | 8 / 17 | |
| 0.3.10 | 8 / 17 | |
| 0.3.9 | 8 / 17 | |
| 0.3.8 | 8 / 17 | |
| 0.3.7 | 8 / 17 | |
| 0.3.6 | 8 / 17 | |
| 0.3.5 | 8 / 17 | |
| 0.3.4 | 8 / 17 | |
| 0.3.3 | 8 / 17 | |
| 0.3.2 | 8 / 17 | |
| 0.3.0 | 8 / 16 | |
| 0.2.42 | 8 / 15 | |
| 0.2.41 | 8 / 15 | |
| 0.2.37 | 8 / 15 | |
| 0.2.35 | 8 / 15 | |
| 0.2.29 | 8 / 13 | |
| 0.2.28 | 8 / 13 | |
| 0.2.27 | 8 / 13 | |
| 0.2.26 | 8 / 13 | |
| 0.2.25 | 8 / 13 | |
| 0.2.17 | 8 / 13 | |
| 0.2.16 | 8 / 13 | |
| 0.1.22 | 8 / 12 | |
| 0.1.21 | 8 / 12 | |
| 0.1.20 | 8 / 12 | |
| 0.1.12 | 8 / 11 | |
| 0.1.8 | 9 / 10 | |
| 0.1.7 | 9 / 10 | |
| 0.1.6 | 9 / 10 | |
| 0.1.5 | 9 / 7 | |
| 0.1.3 | 9 / 7 | |
| 0.1.2 | 9 / 7 | |
| 0.1.1 | 9 / 7 | |
| 0.1.0 | 9 / 7 | |
| 0.0.9 | 9 / 7 | |
| 0.0.8 | 10 / 7 | |
| 0.0.7 | 10 / 7 | |
| 0.0.6 | 10 / 7 | |
| 0.0.5 | 0 / 36 | |
| 0.0.4 | 0 / 36 | |
| 0.0.3 | 0 / 36 | |
| 0.0.2 | 0 / 35 |
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tvenceslau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tvenceslau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tvenceslau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
2 findingsNewly 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.
v0.0.6
2 findingsNewly 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.
v0.0.5
21 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
v0.0.4
9 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.
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.
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.
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.
v0.0.3
9 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.
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.
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.
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.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.