@bobfrankston/npmglobalize
Transform file: dependencies to npm versions for publishing
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pacote | AI (phantom-deps): Dep is declared and used at runtime via config transform pattern; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:simple-git | AI (phantom-deps): Same config-transform pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:npm-registry-fetch | AI (phantom-deps): Same config-transform pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@npmcli/package-json | AI (phantom-deps): Same config-transform pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@bobfrankston/npmglobalize | AI (phantom-deps): Self-referential dep is intentional per the package's publish-transform purpose. | ai |
Versions (showing 100 of 167)
| Version | Deps | Published |
|---|---|---|
| 1.0.190 | 10 / 3 | |
| 1.0.189 | 10 / 3 | |
| 1.0.188 | 10 / 3 | |
| 1.0.187 | 10 / 3 | |
| 1.0.186 | 10 / 3 | |
| 1.0.185 | 10 / 3 | |
| 1.0.184 | 10 / 3 | |
| 1.0.183 | 12 / 3 | |
| 1.0.182 | 12 / 3 | |
| 1.0.181 | 12 / 3 | |
| 1.0.180 | 12 / 3 | |
| 1.0.179 | 12 / 3 | |
| 1.0.178 | 12 / 3 | |
| 1.0.177 | 12 / 3 | |
| 1.0.176 | 12 / 3 | |
| 1.0.175 | 12 / 3 | |
| 1.0.174 | 12 / 3 | |
| 1.0.173 | 11 / 3 | |
| 1.0.172 | 11 / 3 | |
| 1.0.171 | 11 / 3 | |
| 1.0.170 | 11 / 3 | |
| 1.0.169 | 11 / 3 | |
| 1.0.168 | 11 / 3 | |
| 1.0.167 | 11 / 3 | |
| 1.0.166 | 11 / 3 | |
| 1.0.165 | 11 / 3 | |
| 1.0.164 | 11 / 3 | |
| 1.0.163 | 11 / 3 | |
| 1.0.162 | 11 / 3 | |
| 1.0.161 | 11 / 3 | |
| 1.0.160 | 11 / 3 | |
| 1.0.159 | 11 / 3 | |
| 1.0.158 | 11 / 3 | |
| 1.0.157 | 11 / 3 | |
| 1.0.156 | 11 / 3 | |
| 1.0.155 | 11 / 3 | |
| 1.0.154 | 11 / 3 | |
| 1.0.153 | 10 / 3 | |
| 1.0.152 | 10 / 3 | |
| 1.0.151 | 10 / 3 | |
| 1.0.150 | 10 / 3 | |
| 1.0.149 | 10 / 3 | |
| 1.0.148 | 10 / 3 | |
| 1.0.147 | 10 / 3 | |
| 1.0.146 | 10 / 3 | |
| 1.0.145 | 10 / 3 | |
| 1.0.144 | 10 / 3 | |
| 1.0.143 | 10 / 3 | |
| 1.0.142 | 10 / 3 | |
| 1.0.141 | 10 / 3 | |
| 1.0.140 | 10 / 3 | |
| 1.0.139 | 10 / 3 | |
| 1.0.138 | 10 / 3 | |
| 1.0.137 | 9 / 3 | |
| 1.0.136 | 9 / 3 | |
| 1.0.135 | 9 / 3 | |
| 1.0.134 | 9 / 3 | |
| 1.0.133 | 9 / 3 | |
| 1.0.132 | 9 / 3 | |
| 1.0.131 | 9 / 3 | |
| 1.0.130 | 9 / 3 | |
| 1.0.129 | 9 / 3 | |
| 1.0.128 | 9 / 3 | |
| 1.0.127 | 9 / 3 | |
| 1.0.126 | 9 / 3 | |
| 1.0.125 | 9 / 3 | |
| 1.0.124 | 9 / 3 | |
| 1.0.123 | 9 / 3 | |
| 1.0.122 | 9 / 3 | |
| 1.0.121 | 9 / 3 | |
| 1.0.120 | 9 / 3 | |
| 1.0.119 | 9 / 3 | |
| 1.0.118 | 9 / 3 | |
| 1.0.117 | 9 / 3 | |
| 1.0.116 | 8 / 3 | |
| 1.0.115 | 8 / 3 | |
| 1.0.114 | 8 / 3 | |
| 1.0.113 | 8 / 3 | |
| 1.0.112 | 8 / 3 | |
| 1.0.111 | 8 / 3 | |
| 1.0.110 | 8 / 3 | |
| 1.0.109 | 7 / 3 | |
| 1.0.108 | 7 / 3 | |
| 1.0.107 | 7 / 3 | |
| 1.0.106 | 7 / 3 | |
| 1.0.105 | 7 / 3 | |
| 1.0.104 | 7 / 3 | |
| 1.0.103 | 7 / 3 | |
| 1.0.102 | 7 / 3 | |
| 1.0.101 | 7 / 3 | |
| 1.0.100 | 7 / 3 | |
| 1.0.99 | 7 / 3 | |
| 1.0.98 | 7 / 3 | |
| 1.0.97 | 7 / 3 | |
| 1.0.96 | 7 / 3 | |
| 1.0.95 | 7 / 3 | |
| 1.0.94 | 7 / 3 | |
| 1.0.93 | 7 / 3 | |
| 1.0.92 | 6 / 3 | |
| 1.0.91 | 6 / 3 |
v1.0.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.168
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.