@mxpicture/build-api
Build utilities API
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package is published via GitHub Actions CI/CD; lack of Sigstore provenance is common and not a security threat for this org's packages. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a legitimate build utility dependency used indirectly by this package's utilities; phantom-dep pattern is expected for utility libraries. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): micromatch is a legitimate build utility dependency used indirectly; phantom-dep pattern is expected for utility libraries. | ai | |
| phantom-deps | phantom-dep:@commander-js/extra-typings | AI (phantom-deps): Type definitions package used indirectly with commander; phantom-dep pattern is expected for utility libraries. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type definition package for a TypeScript build utilities library; declaring it as a dep without direct imports is standard practice. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Referenced in config files rather than direct imports; expected pattern for ESLint plugin dependencies in a build utilities package. | ai | |
| phantom-deps | phantom-dep:@types/micromatch | AI (phantom-deps): @types/micromatch is a TypeScript type declaration package; declaring it as a dependency without direct imports is standard practice in TypeScript projects. | ai | |
| phantom-deps | phantom-dep:@mxpicture/dep-analyzer | AI (phantom-deps): Same-org scoped package from @mxpicture; phantom usage is consistent with internal tooling loaded indirectly or via dist output. | ai |
Versions (showing 100 of 232)
| Version | Deps | Published |
|---|---|---|
| 0.3.39 | 14 / 0 | |
| 0.3.38 | 14 / 0 | |
| 0.3.37 | 14 / 0 | |
| 0.3.36 | 14 / 0 | |
| 0.3.35 | 14 / 0 | |
| 0.3.34 | 14 / 0 | |
| 0.3.33 | 14 / 0 | |
| 0.3.32 | 14 / 0 | |
| 0.3.31 | 14 / 0 | |
| 0.3.30 | 14 / 0 | |
| 0.3.29 | 15 / 0 | |
| 0.3.28 | 15 / 0 | |
| 0.3.27 | 15 / 0 | |
| 0.3.26 | 15 / 0 | |
| 0.3.25 | 15 / 0 | |
| 0.3.24 | 15 / 0 | |
| 0.3.23 | 15 / 0 | |
| 0.3.22 | 15 / 0 | |
| 0.3.21 | 15 / 0 | |
| 0.3.20 | 15 / 0 | |
| 0.3.19 | 15 / 0 | |
| 0.3.18 | 15 / 0 | |
| 0.3.17 | 15 / 0 | |
| 0.3.16 | 15 / 0 | |
| 0.3.10 | 15 / 0 | |
| 0.3.9 | 15 / 0 | |
| 0.3.8 | 15 / 0 | |
| 0.3.7 | 15 / 0 | |
| 0.3.6 | 15 / 0 | |
| 0.3.5 | 15 / 0 | |
| 0.3.4 | 14 / 1 | |
| 0.3.3 | 14 / 1 | |
| 0.3.2 | 14 / 1 | |
| 0.2.107 | 14 / 0 | |
| 0.2.106 | 14 / 0 | |
| 0.2.105 | 14 / 0 | |
| 0.2.104 | 14 / 0 | |
| 0.2.103 | 14 / 0 | |
| 0.2.102 | 14 / 0 | |
| 0.2.101 | 11 / 0 | |
| 0.2.100 | 11 / 0 | |
| 0.2.99 | 11 / 0 | |
| 0.2.98 | 11 / 0 | |
| 0.2.97 | 11 / 0 | |
| 0.2.96 | 11 / 0 | |
| 0.2.95 | 11 / 0 | |
| 0.2.94 | 11 / 0 | |
| 0.2.93 | 11 / 0 | |
| 0.2.92 | 11 / 0 | |
| 0.2.91 | 11 / 0 | |
| 0.2.90 | 11 / 0 | |
| 0.2.89 | 11 / 0 | |
| 0.2.88 | 11 / 0 | |
| 0.2.87 | 11 / 0 | |
| 0.2.86 | 11 / 0 | |
| 0.2.85 | 11 / 0 | |
| 0.2.84 | 11 / 0 | |
| 0.2.83 | 11 / 0 | |
| 0.2.82 | 11 / 0 | |
| 0.2.81 | 11 / 0 | |
| 0.2.80 | 11 / 0 | |
| 0.2.79 | 11 / 0 | |
| 0.2.78 | 11 / 0 | |
| 0.2.77 | 12 / 0 | |
| 0.2.76 | 11 / 0 | |
| 0.2.75 | 11 / 0 | |
| 0.2.74 | 11 / 0 | |
| 0.2.73 | 11 / 0 | |
| 0.2.72 | 11 / 0 | |
| 0.2.71 | 11 / 0 | |
| 0.2.70 | 11 / 0 | |
| 0.2.69 | 11 / 0 | |
| 0.2.68 | 11 / 0 | |
| 0.2.67 | 11 / 0 | |
| 0.2.66 | 11 / 0 | |
| 0.2.65 | 11 / 0 | |
| 0.2.64 | 11 / 0 | |
| 0.2.63 | 11 / 0 | |
| 0.2.62 | 11 / 0 | |
| 0.2.61 | 11 / 0 | |
| 0.2.60 | 11 / 0 | |
| 0.2.59 | 11 / 0 | |
| 0.2.58 | 10 / 0 | |
| 0.2.57 | 8 / 0 | |
| 0.2.56 | 8 / 0 | |
| 0.2.55 | 8 / 0 | |
| 0.2.54 | 8 / 0 | |
| 0.2.53 | 8 / 0 | |
| 0.2.52 | 8 / 0 | |
| 0.2.51 | 8 / 0 | |
| 0.2.50 | 8 / 0 | |
| 0.2.49 | 8 / 0 | |
| 0.2.48 | 7 / 1 | |
| 0.2.45 | 7 / 1 | |
| 0.2.44 | 7 / 1 | |
| 0.2.43 | 7 / 1 | |
| 0.2.42 | 7 / 1 | |
| 0.2.41 | 7 / 1 | |
| 0.2.39 | 7 / 1 | |
| 0.2.37 | 7 / 1 |
v0.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.