@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.4.42 | 16 / 0 | |
| 0.4.41 | 16 / 0 | |
| 0.4.40 | 16 / 0 | |
| 0.4.39 | 16 / 0 | |
| 0.4.37 | 15 / 0 | |
| 0.4.36 | 15 / 0 | |
| 0.4.35 | 15 / 0 | |
| 0.4.34 | 15 / 0 | |
| 0.4.33 | 15 / 0 | |
| 0.4.32 | 15 / 0 | |
| 0.4.31 | 15 / 0 | |
| 0.4.23 | 15 / 0 | |
| 0.4.22 | 15 / 0 | |
| 0.4.21 | 15 / 0 | |
| 0.4.20 | 15 / 0 | |
| 0.4.19 | 15 / 0 | |
| 0.4.18 | 15 / 0 | |
| 0.4.17 | 14 / 0 | |
| 0.4.16 | 14 / 0 | |
| 0.4.15 | 14 / 0 | |
| 0.4.14 | 14 / 0 | |
| 0.4.13 | 14 / 0 | |
| 0.4.12 | 14 / 0 | |
| 0.4.11 | 14 / 0 | |
| 0.4.10 | 14 / 0 | |
| 0.4.9 | 14 / 0 | |
| 0.4.8 | 14 / 0 | |
| 0.4.7 | 14 / 0 | |
| 0.4.6 | 14 / 0 | |
| 0.4.5 | 14 / 0 | |
| 0.4.4 | 14 / 0 | |
| 0.4.3 | 14 / 0 | |
| 0.4.2 | 14 / 0 | |
| 0.3.106 | 14 / 0 | |
| 0.3.105 | 14 / 0 | |
| 0.3.104 | 14 / 0 | |
| 0.3.103 | 14 / 0 | |
| 0.3.102 | 14 / 0 | |
| 0.3.101 | 14 / 0 | |
| 0.3.100 | 14 / 0 | |
| 0.3.99 | 14 / 0 | |
| 0.3.98 | 14 / 0 | |
| 0.3.97 | 14 / 0 | |
| 0.3.96 | 15 / 1 | |
| 0.3.95 | 15 / 1 | |
| 0.3.94 | 15 / 1 | |
| 0.3.93 | 15 / 1 | |
| 0.3.92 | 15 / 1 | |
| 0.3.91 | 15 / 1 | |
| 0.3.90 | 15 / 1 | |
| 0.3.89 | 15 / 1 | |
| 0.3.88 | 15 / 1 | |
| 0.3.87 | 15 / 1 | |
| 0.3.86 | 15 / 1 | |
| 0.3.85 | 15 / 1 | |
| 0.3.84 | 15 / 1 | |
| 0.3.83 | 15 / 1 | |
| 0.3.82 | 15 / 1 | |
| 0.3.81 | 15 / 1 | |
| 0.3.80 | 15 / 1 | |
| 0.3.79 | 15 / 1 | |
| 0.3.78 | 15 / 1 | |
| 0.3.77 | 15 / 1 | |
| 0.3.76 | 15 / 1 | |
| 0.3.75 | 15 / 1 | |
| 0.3.74 | 15 / 1 | |
| 0.3.73 | 15 / 1 | |
| 0.3.72 | 15 / 1 | |
| 0.3.71 | 15 / 1 | |
| 0.3.70 | 15 / 1 | |
| 0.3.69 | 15 / 1 | |
| 0.3.68 | 15 / 1 | |
| 0.3.67 | 15 / 1 | |
| 0.3.66 | 15 / 1 | |
| 0.3.65 | 15 / 1 | |
| 0.3.64 | 15 / 1 | |
| 0.3.63 | 15 / 1 | |
| 0.3.62 | 15 / 1 | |
| 0.3.61 | 14 / 0 | |
| 0.3.60 | 14 / 0 | |
| 0.3.59 | 14 / 0 | |
| 0.3.58 | 14 / 0 | |
| 0.3.57 | 14 / 0 | |
| 0.3.56 | 14 / 0 | |
| 0.3.55 | 14 / 0 | |
| 0.3.54 | 14 / 0 | |
| 0.3.53 | 14 / 0 | |
| 0.3.52 | 14 / 0 | |
| 0.3.51 | 14 / 0 | |
| 0.3.50 | 14 / 0 | |
| 0.3.49 | 14 / 0 | |
| 0.3.48 | 14 / 0 | |
| 0.3.47 | 14 / 0 | |
| 0.3.46 | 14 / 0 | |
| 0.3.45 | 14 / 0 | |
| 0.3.44 | 14 / 0 | |
| 0.3.43 | 14 / 0 | |
| 0.3.42 | 14 / 0 | |
| 0.3.41 | 14 / 0 | |
| 0.3.40 | 14 / 0 |
v0.4.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.