@eurosat/form
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @eurosat scoped package with long history; lack of Sigstore attestation is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known Angular/TypeScript implicit runtime dependency; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:icon-font-generator | AI (phantom-deps): Referenced in config files per finding; not a direct import but a build-time tool, stable false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Angular form library; Levenshtein match to 'cors' is a false positive with no plausible impersonation intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package with 552 versions and 2860 days of history; missing metadata is cosmetic, not indicative of spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-lived scoped library; missing description is a cosmetic issue, not a risk signal. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 17.0.3 | 2 / 0 | |
| 17.0.2 | 2 / 0 | |
| 17.0.1 | 2 / 0 | |
| 17.0.0 | 2 / 0 | |
| 16.0.4 | 2 / 0 | |
| 16.0.3 | 2 / 0 | |
| 16.0.2 | 2 / 0 | |
| 16.0.1 | 2 / 0 | |
| 16.0.0 | 2 / 0 | |
| 15.0.5 | 2 / 0 | |
| 15.0.4 | 2 / 0 |
v17.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.