@esfaenza/forms-and-validations
This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.2.0.
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): Long-lived internal Angular library; sparse metadata is typical for private org packages, not malware. | ai |
Versions (showing 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 20.3.4 | 1 / 0 | |
| 20.3.3 | 1 / 0 | |
| 20.3.2 | 1 / 0 | |
| 20.3.1 | 1 / 0 | |
| 20.3.0 | 1 / 0 | |
| 19.2.102 | 1 / 0 | |
| 19.2.101 | 1 / 0 | |
| 19.2.99 | 1 / 0 | |
| 19.2.98 | 1 / 0 | |
| 19.2.97 | 1 / 0 | |
| 19.2.96 | 1 / 0 | |
| 19.2.95 | 1 / 0 | |
| 19.2.94 | 1 / 0 | |
| 19.2.93 | 1 / 0 | |
| 19.2.92 | 1 / 0 | |
| 19.2.91 | 1 / 0 | |
| 19.2.90 | 1 / 0 | |
| 19.2.89 | 1 / 0 | |
| 19.2.88 | 1 / 0 | |
| 19.2.87 | 1 / 0 | |
| 19.2.86 | 1 / 0 | |
| 19.2.85 | 1 / 0 | |
| 19.2.84 | 1 / 0 | |
| 19.2.83 | 1 / 0 | |
| 19.2.82 | 1 / 0 | |
| 19.2.81 | 1 / 0 | |
| 19.2.80 | 1 / 0 | |
| 19.2.79 | 1 / 0 | |
| 19.2.78 | 1 / 0 | |
| 19.2.77 | 1 / 0 | |
| 19.2.76 | 1 / 0 | |
| 19.2.75 | 1 / 0 | |
| 19.2.74 | 1 / 0 | |
| 19.2.73 | 1 / 0 | |
| 19.2.71 | 1 / 0 | |
| 19.2.70 | 1 / 0 | |
| 19.2.69 | 1 / 0 | |
| 19.2.68 | 1 / 0 | |
| 19.2.67 | 1 / 0 | |
| 19.2.66 | 1 / 0 | |
| 19.2.65 | 1 / 0 | |
| 19.2.64 | 1 / 0 | |
| 19.2.63 | 1 / 0 | |
| 19.2.62 | 1 / 0 | |
| 19.2.61 | 1 / 0 | |
| 19.2.60 | 1 / 0 | |
| 19.2.59 | 1 / 0 | |
| 19.2.58 | 1 / 0 | |
| 19.2.57 | 1 / 0 | |
| 19.2.56 | 1 / 0 | |
| 19.2.55 | 1 / 0 |
v20.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.