microbundle
Zero-configuration bundler for tiny JS libs, powered by Rollup.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:rollup-plugin-alias | AI (dependencies): rollup-plugin-alias is a standard rollup ecosystem plugin for path aliasing, appropriate for a bundler tool like microbundle. | ai | |
| provenance | publisher-changed | AI (provenance): The transition from 'harmony' to 'developit' is a legitimate account consolidation by Jason Miller (the package author). developit is the canonical npm account for this package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): microbundle is a bundler that loads babel plugins by convention; @babel/core is a framework-scoped peer dependency, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/polyfill | AI (phantom-deps): Polyfill injected at runtime by convention in bundler context, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-es3 | AI (phantom-deps): Rollup plugin referenced in config files rather than direct imports; expected pattern for a bundler tool. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-sizes | AI (phantom-deps): Rollup plugin referenced in config files rather than direct imports; expected pattern for a bundler tool. | ai | |
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Babel presets are loaded by convention via @rollup/plugin-babel; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/preset-flow | AI (phantom-deps): Babel presets are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/preset-react | AI (phantom-deps): Babel presets are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:babel-plugin-macros | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-jsx | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-bundle-size | AI (phantom-deps): Rollup plugin loaded via config; indirect usage is expected for a bundler tool. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load the user's locally-installed TypeScript via resolveFrom — a standard optional peer-dep loading pattern for build tools. Not a security risk. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-regenerator | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-class-properties | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-flow-strip-types | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-async-to-promises | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance; absence of attestation is not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-import-meta | AI (phantom-deps): Babel plugins are loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript is an optional peer dep loaded dynamically at runtime; the dynamic-require pattern is intentional for microbundle's architecture. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a runtime helper injected by TypeScript compilation; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:terser | AI (phantom-deps): terser is loaded via rollup-plugin-terser config; indirect usage is expected for a bundler tool. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is loaded via rollup-plugin-postcss; indirect usage is expected for a bundler tool. | ai | |
| phantom-deps | phantom-dep:filesize | AI (phantom-deps): filesize is referenced in config/plugin context; indirect usage is expected for a bundler tool. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.15.1 | 42 / 23 | |
| 0.15.0 | 42 / 24 | |
| 0.14.2 | 41 / 24 | |
| 0.14.1 | 41 / 24 | |
| 0.14.0 | 41 / 24 | |
| 0.13.3 | 40 / 24 | |
| 0.13.2 | 40 / 24 | |
| 0.13.1 | 39 / 24 | |
| 0.13.0 | 39 / 24 | |
| 0.12.4 | 42 / 24 | |
| 0.12.3 | 41 / 23 | |
| 0.12.2 | 41 / 23 | |
| 0.12.1 | 41 / 23 | |
| 0.12.0 | 37 / 24 | |
| 0.11.0 | 33 / 20 | |
| 0.10.1 | 33 / 20 | |
| 0.10.0 | 32 / 20 | |
| 0.9.0 | 32 / 20 | |
| 0.8.4 | 33 / 20 | |
| 0.8.3 | 32 / 19 | |
| 0.8.2 | 32 / 19 | |
| 0.8.1 | 32 / 19 | |
| 0.8.0 | 32 / 19 | |
| 0.7.0 | 29 / 15 | |
| 0.6.0 | 28 / 15 | |
| 0.5.1 | 29 / 15 | |
| 0.4.4 | 28 / 8 | |
| 0.4.3 | 28 / 8 | |
| 0.4.2 | 29 / 8 | |
| 0.4.1 | 29 / 7 | |
| 0.4.0 | 28 / 7 | |
| 0.3.1 | 26 / 4 | |
| 0.3.0 | 26 / 4 | |
| 0.2.4 | 20 / 4 | |
| 0.2.3 | 19 / 4 | |
| 0.2.2 | 19 / 4 | |
| 0.2.1 | 19 / 4 | |
| 0.2.0 | 19 / 4 | |
| 0.1.1 | 18 / 4 | |
| 0.1.0 | 18 / 4 |
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version was published by a different npm account than previous versions on 2020-12-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
2 findingsThis version was published by a different npm account than previous versions on 2020-09-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findingsThis version was published by a different npm account than previous versions on 2019-02-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
2 findingsThis version was published by a different npm account than previous versions on 2018-12-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
2 findingsThis version was published by a different npm account than previous versions on 2018-12-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsThis version was published by a different npm account than previous versions on 2018-12-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version was published by a different npm account than previous versions on 2018-11-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
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.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.