@platforma-open/milaboratories.graph-maker
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@platforma-open/milaboratories.graph-maker.ui | AI (phantom-deps): Same-org sub-package referenced via block config path, not direct import; stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.graph-maker.model | AI (phantom-deps): Same-org sub-package referenced via block config path, not direct import; stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.graph-maker.workflow | AI (phantom-deps): Same-org sub-package referenced via block config path, not direct import; stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): SDK dep referenced in block config, not direct import; stable false positive for this package type. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.4.95 | 4 / 1 | |
| 1.4.94 | 4 / 1 | |
| 1.4.93 | 4 / 1 | |
| 1.4.92 | 4 / 1 | |
| 1.4.91 | 4 / 1 | |
| 1.4.88 | 4 / 1 | |
| 1.4.85 | 4 / 1 | |
| 1.4.83 | 4 / 1 | |
| 1.4.82 | 4 / 1 | |
| 1.4.81 | 4 / 1 | |
| 1.4.79 | 4 / 1 | |
| 1.4.76 | 4 / 1 | |
| 1.4.74 | 4 / 1 | |
| 1.4.73 | 4 / 1 | |
| 1.4.72 | 4 / 1 | |
| 1.4.71 | 4 / 1 | |
| 1.4.64 | 4 / 1 | |
| 1.4.61 | 4 / 1 | |
| 1.4.55 | 4 / 1 | |
| 1.4.47 | 4 / 1 | |
| 1.4.46 | 4 / 1 | |
| 1.4.44 | 4 / 1 | |
| 1.4.42 | 4 / 1 | |
| 1.4.38 | 4 / 1 | |
| 1.4.33 | 4 / 1 |
v1.4.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.