@meshmakers/shared-auth
OAuth2/OIDC authentication library for Angular applications using [angular-oauth2-oidc](https://github.com/manfredsteyer/angular-oauth2-oidc).
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:fesm2022/meshmakers-shared-auth-login-ui.mjs | AI (source-diff): Standard Angular FESM2022 bundle output; long lines are normal for Angular compiler-generated code. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency; phantom-dep false positive for Angular packages. | ai |
Versions (showing 51 of 163)
| Version | Deps | Published |
|---|---|---|
| 3.4.600 | 1 / 0 | |
| 3.4.550 | 1 / 0 | |
| 3.4.530 | 1 / 0 | |
| 3.4.520 | 1 / 0 | |
| 3.4.510 | 1 / 0 | |
| 3.4.500 | 1 / 0 | |
| 3.4.490 | 1 / 0 | |
| 3.4.470 | 1 / 0 | |
| 3.4.460 | 1 / 0 | |
| 3.4.450 | 1 / 0 | |
| 3.4.440 | 1 / 0 | |
| 3.4.420 | 1 / 0 | |
| 3.4.410 | 1 / 0 | |
| 3.4.400 | 1 / 0 | |
| 3.4.380 | 1 / 0 | |
| 3.4.370 | 1 / 0 | |
| 3.4.360 | 1 / 0 | |
| 3.4.350 | 1 / 0 | |
| 3.4.340 | 1 / 0 | |
| 3.4.330 | 1 / 0 | |
| 3.4.320 | 1 / 0 | |
| 3.4.310 | 1 / 0 | |
| 3.4.290 | 1 / 0 | |
| 3.4.280 | 1 / 0 | |
| 3.4.270 | 1 / 0 | |
| 3.4.260 | 1 / 0 | |
| 3.4.250 | 1 / 0 | |
| 3.4.240 | 1 / 0 | |
| 3.4.230 | 1 / 0 | |
| 3.4.220 | 1 / 0 | |
| 3.4.210 | 1 / 0 | |
| 3.4.200 | 1 / 0 | |
| 3.4.190 | 1 / 0 | |
| 3.4.180 | 1 / 0 | |
| 3.4.170 | 1 / 0 | |
| 3.4.160 | 1 / 0 | |
| 3.4.150 | 1 / 0 | |
| 3.4.140 | 1 / 0 | |
| 3.4.130 | 1 / 0 | |
| 3.4.120 | 1 / 0 | |
| 3.4.110 | 1 / 0 | |
| 3.4.100 | 1 / 0 | |
| 3.4.90 | 1 / 0 | |
| 3.4.70 | 1 / 0 | |
| 3.4.50 | 1 / 0 | |
| 3.3.1210 | 1 / 0 | |
| 3.3.1200 | 1 / 0 | |
| 3.3.1190 | 1 / 0 | |
| 3.3.1180 | 1 / 0 | |
| 3.3.1170 | 1 / 0 | |
| 3.3.1160 | 1 / 0 |
v3.4.600
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.550
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.530
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.520
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.510
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.500
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.490
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.470
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.460
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.450
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.440
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.420
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.410
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.400
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.380
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.370
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.360
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.350
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.340
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.330
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.320
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.310
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.290
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.280
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.