@decaf-ts/transactional-decorators
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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/esm/transactional-decorators.js | AI (source-diff): Webpack-bundled dist build, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/transactional-decorators.js | AI (source-diff): Webpack UMD bundle output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/transactional-decorators.cjs | AI (source-diff): Rollup UMD bundle with readable JSDoc source, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@decaf-ts/decorator-validation | AI (phantom-deps): Same org scope; likely a transitive/peer dep not directly imported in this package. | ai | |
| phantom-deps | phantom-dep:@decaf-ts/injectable-decorators | AI (phantom-deps): Same org scope; likely a transitive/peer dep not directly imported in this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy trap to conditionally suppress log calls — standard TypeScript decorator/proxy pattern, not obfuscation. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 4 / 3 | |
| 0.11.0 | 4 / 3 | |
| 0.10.0 | 4 / 3 | |
| 0.9.0 | 4 / 3 | |
| 0.8.0 | 4 / 3 | |
| 0.7.0 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.0 | 4 / 3 | |
| 0.4.5 | 4 / 3 | |
| 0.4.4 | 4 / 3 | |
| 0.4.3 | 4 / 3 | |
| 0.4.2 | 4 / 3 | |
| 0.4.1 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.9 | 4 / 3 | |
| 0.3.8 | 4 / 3 | |
| 0.3.7 | 4 / 3 | |
| 0.3.6 | 4 / 2 | |
| 0.3.5 | 4 / 2 | |
| 0.3.4 | 4 / 2 | |
| 0.3.3 | 4 / 2 | |
| 0.3.2 | 4 / 2 | |
| 0.3.1 | 4 / 2 | |
| 0.3.0 | 4 / 2 | |
| 0.2.2 | 4 / 2 | |
| 0.2.1 | 4 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.5 | 0 / 2 | |
| 0.1.4 | 0 / 27 | |
| 0.1.3 | 0 / 31 | |
| 0.1.2 | 0 / 31 | |
| 0.1.1 | 0 / 31 | |
| 0.1.0 | 0 / 31 | |
| 0.0.22 | 0 / 39 | |
| 0.0.21 | 0 / 37 | |
| 0.0.20 | 0 / 37 | |
| 0.0.19 | 0 / 37 | |
| 0.0.18 | 0 / 37 | |
| 0.0.17 | 0 / 37 | |
| 0.0.16 | 0 / 37 | |
| 0.0.15 | 0 / 37 | |
| 0.0.14 | 0 / 37 | |
| 0.0.13 | 0 / 37 | |
| 0.0.12 | 0 / 37 | |
| 0.0.11 | 0 / 37 | |
| 0.0.10 | 0 / 37 | |
| 0.0.9 | 0 / 37 | |
| 0.0.8 | 0 / 37 | |
| 0.0.7 | 2 / 37 | |
| 0.0.6 | 2 / 37 | |
| 0.0.5 | 0 / 37 |
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
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.22
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.