← Home

@mapbox/unitbezier

npm Repository Homepage

unit bezier curve interpolation

2
Versions
BSD-2-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mapbox-npm-01mapbox-npm-02mapbox-npm-07mapbox-npm-03mapbox-npm-04mapbox-npm-09mapbox-npm-05mapbox-npm-06mapbox-npm-08mapbox-npm-advanced-actionsmapbox-npm-cimapbox-npmmapbox-adminmapbox-machine-usermbx-npm-ci-stagingmbx-npm-ci-productionmbx-npm-01-productionmbx-npm-02-productionmbx-npm-03-productionmbx-npm-04-productionmbx-npm-05-productionmbx-npm-06-productionmbx-npm-07-productionmbx-npm-08-productionmbx-npm-09-productionmbx-npm-02-stagingmbx-npm-advanced-actions-stagingmbx-npm-advanced-actions-production

Keywords

unitbezierinterpolationwebkit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Mapbox org-wide CI bot rotation; all new maintainers follow mbx-npm-* naming convention. ai
provenance publisher-changed AI (provenance): Legitimate Mapbox org publisher rotation from mapbox-npm to mbx-npm-03-production. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by stable tiny library; v1.0.0 is an ESM migration. ai

Versions (showing 2 of 2)

Version Deps Published
1.0.0 0 / 2
0.0.1 0 / 3

v1.0.0

2 findings
HIGH Publisher changed: mapbox-npm → mbx-npm-03-production (on 2026-05-26) provenance

This version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.