@milaboratories/pl-model-middle-layer
Common model between middle layer and non-block UI code
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): mike-ainsel is an established publisher in the same org with 915 approved packages; transition appears legitimate. | ai | |
| phantom-deps | phantom-dep:@milaboratories/helpers | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for re-exported type packages in monorepos. | ai |
Versions (showing 100 of 230)
| Version | Deps | Published |
|---|---|---|
| 1.8.38 | 4 / 5 | |
| 1.8.37 | 4 / 4 | |
| 1.8.36 | 4 / 4 | |
| 1.8.35 | 4 / 4 | |
| 1.8.34 | 4 / 4 | |
| 1.8.33 | 4 / 4 | |
| 1.8.32 | 4 / 4 | |
| 1.8.31 | 4 / 4 | |
| 1.8.30 | 4 / 4 | |
| 1.8.29 | 4 / 4 | |
| 1.8.28 | 4 / 4 | |
| 1.8.27 | 4 / 4 | |
| 1.8.26 | 4 / 4 | |
| 1.8.25 | 4 / 4 | |
| 1.8.24 | 4 / 4 | |
| 1.8.23 | 4 / 4 | |
| 1.8.22 | 4 / 4 | |
| 1.8.21 | 4 / 4 | |
| 1.8.20 | 4 / 4 | |
| 1.8.19 | 4 / 4 | |
| 1.8.18 | 4 / 4 | |
| 1.8.17 | 4 / 4 | |
| 1.8.16 | 4 / 4 | |
| 1.8.15 | 4 / 4 | |
| 1.8.14 | 4 / 4 | |
| 1.8.13 | 4 / 4 | |
| 1.8.12 | 4 / 4 | |
| 1.8.11 | 4 / 4 | |
| 1.8.10 | 4 / 4 | |
| 1.8.9 | 4 / 4 | |
| 1.8.8 | 4 / 4 | |
| 1.8.7 | 4 / 3 | |
| 1.8.6 | 4 / 3 | |
| 1.8.5 | 4 / 3 | |
| 1.8.4 | 4 / 3 | |
| 1.8.3 | 4 / 3 | |
| 1.8.2 | 4 / 3 | |
| 1.8.1 | 4 / 3 | |
| 1.8.0 | 4 / 3 | |
| 1.7.52 | 4 / 3 | |
| 1.7.51 | 4 / 3 | |
| 1.7.50 | 4 / 3 | |
| 1.7.49 | 4 / 3 | |
| 1.7.48 | 4 / 3 | |
| 1.7.47 | 4 / 3 | |
| 1.7.46 | 4 / 3 | |
| 1.7.45 | 4 / 3 | |
| 1.7.44 | 4 / 3 | |
| 1.7.43 | 4 / 3 | |
| 1.7.42 | 4 / 3 | |
| 1.7.41 | 4 / 3 | |
| 1.7.40 | 4 / 3 | |
| 1.7.39 | 4 / 3 | |
| 1.7.38 | 4 / 3 | |
| 1.7.37 | 4 / 3 | |
| 1.7.36 | 4 / 3 | |
| 1.7.35 | 4 / 3 | |
| 1.7.34 | 4 / 3 | |
| 1.7.33 | 4 / 3 | |
| 1.7.32 | 4 / 3 | |
| 1.7.31 | 4 / 3 | |
| 1.7.30 | 4 / 3 | |
| 1.7.29 | 4 / 3 | |
| 1.7.28 | 4 / 3 | |
| 1.7.27 | 4 / 3 | |
| 1.7.26 | 4 / 3 | |
| 1.7.25 | 4 / 3 | |
| 1.7.24 | 4 / 3 | |
| 1.7.23 | 4 / 3 | |
| 1.7.22 | 4 / 3 | |
| 1.7.21 | 4 / 3 | |
| 1.7.20 | 4 / 3 | |
| 1.7.19 | 4 / 3 | |
| 1.7.18 | 4 / 3 | |
| 1.7.17 | 4 / 3 | |
| 1.7.16 | 4 / 3 | |
| 1.7.15 | 4 / 3 | |
| 1.7.14 | 4 / 3 | |
| 1.7.13 | 4 / 3 | |
| 1.7.12 | 4 / 3 | |
| 1.7.11 | 4 / 3 | |
| 1.7.10 | 4 / 3 | |
| 1.7.9 | 4 / 3 | |
| 1.7.8 | 4 / 3 | |
| 1.7.7 | 4 / 3 | |
| 1.7.6 | 4 / 3 | |
| 1.7.5 | 4 / 3 | |
| 1.7.4 | 4 / 3 | |
| 1.7.3 | 4 / 3 | |
| 1.7.2 | 4 / 3 | |
| 1.7.1 | 4 / 3 | |
| 1.7.0 | 4 / 3 | |
| 1.6.11 | 4 / 3 | |
| 1.6.10 | 4 / 3 | |
| 1.6.9 | 4 / 3 | |
| 1.6.8 | 4 / 3 | |
| 1.6.7 | 4 / 3 | |
| 1.6.6 | 4 / 3 | |
| 1.6.5 | 4 / 3 | |
| 1.6.4 | 4 / 3 |
v1.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.