ordered-binary
Conversion of JavaScript primitives to and from Buffer with binary order matching natural primitive order
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is used internally to build an optimized string decoder from internally-constructed code strings — not user input. Legitimate performance pattern consistent with this binary serialization library. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used on internally-constructed code (makeStringBuilder output), not user input. Standard dynamic code generation for performance optimization in this binary codec library. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 0 / 4 | |
| 1.6.0 | 0 / 4 | |
| 1.5.3 | 0 / 4 | |
| 1.5.2 | 0 / 4 | |
| 1.5.1 | 0 / 4 | |
| 1.5.0 | 0 / 4 | |
| 1.4.1 | 0 / 4 | |
| 1.4.0 | 0 / 4 | |
| 1.3.0 | 0 / 4 | |
| 1.2.5 | 0 / 4 | |
| 1.2.4 | 0 / 4 | |
| 1.2.3 | 0 / 4 | |
| 1.2.2 | 0 / 4 | |
| 1.2.1 | 0 / 4 | |
| 1.2.0 | 0 / 4 | |
| 1.1.3 | 0 / 4 | |
| 1.1.2 | 0 / 4 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.0 | 0 / 3 | |
| 0.2.3 | 0 / 3 | |
| 0.2.2 | 0 / 3 | |
| 0.2.1 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 | |
| 0.0.2 | 0 / 3 | |
| 0.0.1 | 0 / 3 |
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.