@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 — 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 |
|---|---|---|---|---|
| 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 51 of 251)
| Version | Deps | Published |
|---|---|---|
| 1.4.48 | 3 / 1 | |
| 1.4.47 | 3 / 1 | |
| 1.4.46 | 3 / 1 | |
| 1.4.45 | 3 / 1 | |
| 1.4.44 | 3 / 1 | |
| 1.4.43 | 3 / 1 | |
| 1.4.42 | 3 / 1 | |
| 1.4.41 | 3 / 1 | |
| 1.4.40 | 3 / 1 | |
| 1.4.39 | 3 / 1 | |
| 1.4.38 | 3 / 1 | |
| 1.4.37 | 3 / 1 | |
| 1.4.36 | 3 / 1 | |
| 1.4.35 | 3 / 1 | |
| 1.4.34 | 3 / 1 | |
| 1.4.33 | 3 / 1 | |
| 1.4.32 | 3 / 1 | |
| 1.4.31 | 3 / 1 | |
| 1.4.30 | 3 / 1 | |
| 1.4.29 | 3 / 1 | |
| 1.4.28 | 3 / 1 | |
| 1.4.27 | 3 / 1 | |
| 1.4.26 | 3 / 1 | |
| 1.4.9 | 3 / 1 | |
| 1.4.6 | 3 / 1 | |
| 1.4.5 | 3 / 1 | |
| 1.4.0 | 3 / 1 | |
| 1.3.36 | 3 / 1 | |
| 1.3.32 | 3 / 1 | |
| 1.3.30 | 3 / 1 | |
| 1.3.27 | 3 / 1 | |
| 1.3.23 | 3 / 1 | |
| 1.3.20 | 3 / 1 | |
| 1.3.19 | 3 / 1 | |
| 1.3.16 | 3 / 1 | |
| 1.3.13 | 3 / 1 | |
| 1.3.8 | 3 / 1 | |
| 1.3.5 | 3 / 1 | |
| 1.3.4 | 3 / 1 | |
| 1.3.3 | 3 / 1 | |
| 1.3.2 | 3 / 1 | |
| 1.3.1 | 3 / 1 | |
| 1.3.0 | 3 / 1 | |
| 1.2.68 | 3 / 1 | |
| 1.2.67 | 3 / 1 | |
| 1.2.66 | 3 / 1 | |
| 1.2.65 | 3 / 1 | |
| 1.2.64 | 3 / 1 | |
| 1.2.63 | 3 / 1 | |
| 1.2.62 | 3 / 1 | |
| 1.2.61 | 3 / 1 |
v1.4.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
2 findingsThis version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.