@milaboratories/milaboratories.monetization-test
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Wrapper/meta-package for milaboratories block; description lives in block.meta. | ai | |
| phantom-deps | phantom-dep:@milaboratories/milaboratories.monetization-test.ui | AI (phantom-deps): Umbrella block package declares sub-block deps for platform resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@milaboratories/milaboratories.monetization-test.model | AI (phantom-deps): Umbrella block package declares sub-block deps for platform resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@milaboratories/milaboratories.monetization-test.workflow | AI (phantom-deps): Umbrella block package declares sub-block deps for platform resolution, not direct import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Meta-package for MiLaboratories platform blocks; tiny payload and missing metadata are expected. | ai |
Versions (showing 100 of 305)
| Version | Deps | Published |
|---|---|---|
| 1.0.104 | 3 / 1 | |
| 1.0.103 | 3 / 1 | |
| 1.0.102 | 3 / 1 | |
| 1.0.101 | 3 / 1 | |
| 1.0.100 | 3 / 1 | |
| 1.0.99 | 3 / 1 | |
| 1.0.98 | 3 / 1 | |
| 1.0.97 | 3 / 1 | |
| 1.0.96 | 3 / 1 | |
| 1.0.95 | 3 / 1 | |
| 1.0.94 | 3 / 1 | |
| 1.0.93 | 3 / 1 | |
| 1.0.92 | 3 / 1 | |
| 1.0.91 | 3 / 1 | |
| 1.0.90 | 3 / 1 | |
| 1.0.89 | 3 / 1 | |
| 1.0.88 | 3 / 1 | |
| 1.0.87 | 3 / 1 | |
| 1.0.86 | 3 / 1 | |
| 1.0.85 | 3 / 1 | |
| 1.0.84 | 3 / 1 | |
| 1.0.83 | 3 / 1 | |
| 1.0.82 | 3 / 1 | |
| 1.0.81 | 3 / 1 | |
| 1.0.80 | 3 / 1 | |
| 1.0.79 | 3 / 1 | |
| 1.0.78 | 3 / 1 | |
| 1.0.77 | 3 / 1 | |
| 1.0.76 | 3 / 1 | |
| 1.0.75 | 3 / 1 | |
| 1.0.74 | 3 / 1 | |
| 1.0.73 | 3 / 1 | |
| 1.0.72 | 3 / 1 | |
| 1.0.71 | 3 / 1 | |
| 1.0.70 | 3 / 1 | |
| 1.0.69 | 3 / 1 | |
| 1.0.68 | 3 / 1 | |
| 1.0.67 | 3 / 1 | |
| 1.0.66 | 3 / 1 | |
| 1.0.65 | 3 / 1 | |
| 1.0.64 | 3 / 1 | |
| 1.0.63 | 3 / 1 | |
| 1.0.62 | 3 / 1 | |
| 1.0.61 | 3 / 1 | |
| 1.0.60 | 3 / 1 | |
| 1.0.59 | 3 / 1 | |
| 1.0.58 | 3 / 1 | |
| 1.0.57 | 3 / 1 | |
| 1.0.56 | 3 / 1 | |
| 1.0.55 | 3 / 1 | |
| 1.0.54 | 3 / 1 | |
| 1.0.53 | 3 / 1 | |
| 1.0.52 | 3 / 1 | |
| 1.0.51 | 3 / 1 | |
| 1.0.50 | 3 / 1 | |
| 1.0.49 | 3 / 1 | |
| 1.0.48 | 3 / 1 | |
| 1.0.47 | 3 / 1 | |
| 1.0.46 | 3 / 1 | |
| 1.0.45 | 3 / 1 | |
| 1.0.44 | 3 / 1 | |
| 1.0.43 | 3 / 1 | |
| 1.0.42 | 3 / 1 | |
| 1.0.41 | 3 / 1 | |
| 1.0.40 | 3 / 1 | |
| 1.0.39 | 3 / 1 | |
| 1.0.38 | 3 / 1 | |
| 1.0.37 | 3 / 1 | |
| 1.0.36 | 3 / 1 | |
| 1.0.35 | 3 / 1 | |
| 1.0.34 | 3 / 1 | |
| 1.0.33 | 3 / 1 | |
| 1.0.32 | 3 / 1 | |
| 1.0.31 | 3 / 1 | |
| 1.0.30 | 3 / 1 | |
| 1.0.29 | 3 / 1 | |
| 1.0.28 | 3 / 1 | |
| 1.0.27 | 3 / 1 | |
| 1.0.26 | 3 / 1 | |
| 1.0.25 | 3 / 1 | |
| 1.0.24 | 3 / 1 | |
| 1.0.23 | 3 / 1 | |
| 1.0.22 | 3 / 1 | |
| 1.0.21 | 3 / 1 | |
| 1.0.20 | 3 / 1 | |
| 1.0.19 | 3 / 1 | |
| 1.0.18 | 3 / 1 | |
| 1.0.17 | 3 / 1 | |
| 1.0.16 | 3 / 1 | |
| 1.0.15 | 3 / 1 | |
| 1.0.14 | 3 / 1 | |
| 1.0.13 | 3 / 1 | |
| 1.0.12 | 3 / 1 | |
| 1.0.11 | 3 / 1 | |
| 1.0.10 | 3 / 1 | |
| 1.0.9 | 3 / 1 | |
| 1.0.8 | 3 / 1 | |
| 1.0.7 | 3 / 1 | |
| 1.0.6 | 3 / 1 | |
| 1.0.5 | 3 / 1 |
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.