mimos
Mime database interface
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from arb to hueniverse occurred in 2016; hueniverse is the well-known hapijs founder with a strong track record. This is a stable historical transition, not a risk. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 2 / 2 | |
| 4.0.1 | 2 / 2 | |
| 4.0.0 | 2 / 2 | |
| 3.0.3 | 2 / 2 | |
| 3.0.2 | 2 / 2 | |
| 3.0.1 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.0.2 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 1 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
2 findingsThis version was published by a different npm account than previous versions on 2016-07-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-05-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.