@decaf-ts/for-angular
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:www/1049.10b030f0de36543b.js | AI (source-diff): Webpack-bundled Ionic component chunk, not obfuscation. | ai | |
| provenance | missing-githead | AI (provenance): No provenance regression signal beyond missing field; benign for this large build. | ai | |
| source-diff | obfuscated-file:fesm2022/decaf-ts-for-angular.mjs | AI (source-diff): Standard Angular FESM2022 bundle; long lines are expected minified output, not obfuscation. Stable for this package. | ai |
Versions (showing 51 of 168)
| Version | Deps | Published |
|---|---|---|
| 0.5.18 | 1 / 0 | |
| 0.5.17 | 1 / 0 | |
| 0.5.16 | 1 / 0 | |
| 0.5.14 | 1 / 0 | |
| 0.5.13 | 1 / 0 | |
| 0.5.12 | 1 / 0 | |
| 0.5.11 | 1 / 0 | |
| 0.5.10 | 1 / 0 | |
| 0.5.9 | 1 / 0 | |
| 0.5.8 | 1 / 0 | |
| 0.5.7 | 1 / 0 | |
| 0.5.6 | 1 / 0 | |
| 0.5.4 | 1 / 0 | |
| 0.5.2 | 1 / 0 | |
| 0.5.1 | 1 / 0 | |
| 0.5.0 | 1 / 0 | |
| 0.3.6 | 1 / 0 | |
| 0.3.5 | 1 / 0 | |
| 0.3.4 | 1 / 0 | |
| 0.2.0 | 1 / 0 | |
| 0.1.68 | 1 / 0 | |
| 0.1.64 | 1 / 0 | |
| 0.1.63 | 1 / 0 | |
| 0.1.62 | 1 / 0 | |
| 0.1.61 | 1 / 0 | |
| 0.1.59 | 1 / 0 | |
| 0.1.58 | 1 / 0 | |
| 0.1.57 | 1 / 0 | |
| 0.1.56 | 1 / 0 | |
| 0.1.55 | 1 / 0 | |
| 0.1.54 | 1 / 0 | |
| 0.1.53 | 1 / 0 | |
| 0.1.52 | 1 / 0 | |
| 0.1.51 | 1 / 0 | |
| 0.1.50 | 1 / 0 | |
| 0.1.49 | 1 / 0 | |
| 0.1.48 | 1 / 0 | |
| 0.1.47 | 1 / 0 | |
| 0.1.45 | 1 / 0 | |
| 0.1.44 | 1 / 0 | |
| 0.1.43 | 1 / 0 | |
| 0.1.42 | 1 / 0 | |
| 0.1.41 | 1 / 0 | |
| 0.1.40 | 1 / 0 | |
| 0.1.39 | 1 / 0 | |
| 0.1.37 | 1 / 0 | |
| 0.1.36 | 1 / 0 | |
| 0.1.35 | 1 / 0 | |
| 0.1.33 | 1 / 0 | |
| 0.1.31 | 1 / 0 | |
| 0.1.29 | 1 / 0 |
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: demersoncarvalho.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (demersoncarvalho) than the most recent previously approved version (tvenceslau) on 2026-07-10, but demersoncarvalho is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.13
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: demersoncarvalho.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (demersoncarvalho) than the most recent previously approved version (tvenceslau) on 2026-07-01, but demersoncarvalho is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.