@decaf-ts/injectable-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/injectable-decorators.cjs | AI (source-diff): Rollup UMD bundle, minified not obfuscated; no malicious behavior present. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap only; publisher has long clean track record, no behavior change. | ai | |
| source-diff | obfuscated-file:dist/esm/injectable-decorators.js | AI (source-diff): Webpack/UMD minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/injectable-decorators.js | AI (source-diff): Webpack/UMD minified build output, not obfuscation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has consistent approval history; dormancy likely reflects development cadence, not takeover. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 1.19.0 | 1 / 3 | |
| 1.18.0 | 1 / 3 | |
| 1.17.0 | 1 / 3 | |
| 1.16.0 | 1 / 3 | |
| 1.15.0 | 1 / 3 | |
| 1.14.0 | 1 / 3 | |
| 1.13.0 | 1 / 3 | |
| 1.12.0 | 1 / 3 | |
| 1.11.0 | 1 / 3 | |
| 1.10.5 | 1 / 3 | |
| 1.10.4 | 1 / 3 | |
| 1.10.3 | 1 / 3 | |
| 1.10.2 | 1 / 3 | |
| 1.10.1 | 1 / 3 | |
| 1.10.0 | 1 / 3 | |
| 1.9.13 | 1 / 3 | |
| 1.9.12 | 1 / 3 | |
| 1.9.11 | 1 / 2 | |
| 1.9.10 | 1 / 2 | |
| 1.9.9 | 1 / 2 | |
| 1.9.8 | 1 / 2 | |
| 1.9.7 | 1 / 2 | |
| 1.9.6 | 1 / 2 | |
| 1.9.5 | 1 / 2 | |
| 1.9.4 | 0 / 2 | |
| 1.9.3 | 0 / 1 | |
| 1.9.2 | 0 / 1 | |
| 1.9.1 | 0 / 27 | |
| 1.9.0 | 0 / 27 | |
| 1.8.0 | 0 / 27 | |
| 1.7.0 | 0 / 26 | |
| 1.6.17 | 0 / 31 | |
| 1.6.16 | 0 / 31 | |
| 1.6.15 | 0 / 31 | |
| 1.6.14 | 0 / 31 | |
| 1.6.13 | 0 / 31 | |
| 1.6.12 | 0 / 31 | |
| 1.6.11 | 0 / 31 | |
| 1.6.10 | 0 / 31 | |
| 1.6.9 | 0 / 31 | |
| 1.6.8 | 0 / 31 | |
| 1.6.7 | 0 / 31 | |
| 1.6.6 | 0 / 31 | |
| 1.6.5 | 0 / 31 | |
| 1.6.4 | 0 / 31 | |
| 1.6.3 | 0 / 31 | |
| 1.6.2 | 0 / 31 | |
| 1.6.1 | 0 / 31 | |
| 1.6.0 | 0 / 31 | |
| 1.5.19 | 0 / 39 | |
| 1.5.15 | 0 / 35 | |
| 1.5.14 | 0 / 35 | |
| 1.5.13 | 0 / 35 | |
| 1.5.12 | 0 / 35 | |
| 1.5.11 | 0 / 35 | |
| 1.5.9 | 0 / 35 | |
| 1.5.8 | 0 / 35 | |
| 1.5.7 | 0 / 35 | |
| 1.5.6 | 0 / 35 | |
| 1.5.5 | 0 / 35 | |
| 1.5.4 | 0 / 35 | |
| 1.5.3 | 0 / 35 | |
| 1.5.2 | 0 / 35 | |
| 1.5.1 | 0 / 35 | |
| 1.5.0 | 0 / 35 | |
| 1.4.4 | 0 / 32 | |
| 1.4.3 | 0 / 32 | |
| 1.4.2 | 0 / 32 | |
| 1.4.1 | 0 / 31 | |
| 1.4.0 | 0 / 31 | |
| 1.3.0 | 0 / 31 |
v1.6.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.
v1.5.19
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.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.