@baloise/web-app-utils
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash.isnumber | AI (phantom-deps): Lodash utility declared as dep; used indirectly via build/config, not a security concern. | ai | |
| phantom-deps | phantom-dep:lodash.camelcase | AI (phantom-deps): Lodash utility declared as dep; used indirectly via build/config, not a security concern. | ai | |
| phantom-deps | phantom-dep:lodash.upperfirst | AI (phantom-deps): Lodash utility declared as dep; used indirectly via build/config, not a security concern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.17.4 | 12 / 17 | |
| 3.17.3 | 12 / 17 | |
| 3.17.2 | 12 / 17 | |
| 3.17.1 | 12 / 17 | |
| 3.16.5 | 12 / 17 | |
| 3.16.4 | 12 / 17 | |
| 3.16.3 | 12 / 17 | |
| 3.16.1 | 12 / 17 | |
| 3.16.0 | 12 / 17 | |
| 3.15.0 | 12 / 17 | |
| 3.14.0 | 12 / 17 |
v3.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.