@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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Library-style package with thin entry point and scoped org namespace; not spam. | ai | |
| phantom-deps | phantom-dep:canonicalize | AI (phantom-deps): Build-time/config-referenced dep in a TS/Vue library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-hierarchy | AI (phantom-deps): Config-referenced dep in a charting library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/d3-scale | AI (phantom-deps): Type-only package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/d3-hierarchy | AI (phantom-deps): Type-only package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ag-grid-community/core | AI (phantom-deps): Config-referenced dep in a grid/chart library; stable false positive. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.4.6 | 12 / 10 | |
| 1.4.5 | 12 / 10 | |
| 1.4.4 | 12 / 10 | |
| 1.4.3 | 12 / 10 | |
| 1.4.2 | 12 / 10 | |
| 1.4.1 | 12 / 10 | |
| 1.4.0 | 12 / 10 | |
| 1.3.4 | 12 / 10 | |
| 1.3.3 | 12 / 10 | |
| 1.3.2 | 12 / 10 | |
| 1.3.1 | 12 / 10 | |
| 1.3.0 | 12 / 10 | |
| 1.2.10 | 12 / 10 | |
| 1.2.9 | 12 / 10 | |
| 1.2.8 | 12 / 10 | |
| 1.2.7 | 12 / 10 | |
| 1.1.220 | 12 / 10 | |
| 1.1.219 | 12 / 10 | |
| 1.1.218 | 12 / 10 | |
| 1.1.217 | 12 / 10 | |
| 1.1.216 | 12 / 10 | |
| 1.1.215 | 12 / 10 | |
| 1.1.214 | 12 / 10 | |
| 1.1.213 | 12 / 10 | |
| 1.1.212 | 12 / 10 | |
| 1.1.211 | 12 / 10 | |
| 1.1.210 | 12 / 10 | |
| 1.1.209 | 12 / 10 | |
| 1.1.208 | 12 / 10 | |
| 1.1.207 | 12 / 10 | |
| 1.1.206 | 12 / 10 | |
| 1.1.205 | 12 / 10 | |
| 1.1.204 | 14 / 10 | |
| 1.1.203 | 14 / 10 | |
| 1.1.202 | 14 / 10 | |
| 1.1.201 | 14 / 10 | |
| 1.1.200 | 14 / 10 | |
| 1.1.199 | 14 / 10 | |
| 1.1.198 | 14 / 10 | |
| 1.1.197 | 14 / 10 | |
| 1.1.196 | 14 / 10 | |
| 1.1.195 | 14 / 10 | |
| 1.1.194 | 14 / 10 | |
| 1.1.193 | 14 / 10 | |
| 1.1.192 | 14 / 10 | |
| 1.1.191 | 14 / 10 | |
| 1.1.190 | 14 / 10 | |
| 1.1.189 | 14 / 10 | |
| 1.1.188 | 14 / 10 | |
| 1.1.187 | 14 / 10 | |
| 1.1.186 | 14 / 10 |
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.