← Home

typewise

npm Repository Homepage

Typewise-structured sorting for arbitrarily complex data structures

11
Versions
MIT
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

deanlandolt

Keywords

typewisetypescomparesortordercollationcomplexstructuresleveldbindexeddbkeyvalue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:ses AI (dependencies): ses is an optional dependency explicitly disabled in browser builds; it's a legitimate Secure EcmaScript sandbox, not directly imported, and consistent with this package's security-conscious design. ai
phantom-deps phantom-dep:ses AI (phantom-deps): ses is an optional dep referenced only in config (browser field disables it); not being directly imported is expected and intentional for this package. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.3 1 / 2
1.0.2 1 / 2
1.0.1 1 / 2
1.0.0 2 / 2
0.8.2 2 / 1
0.8.1 2 / 1
0.7.0 5 / 1
0.6.0 6 / 1
0.5.0 5 / 1
0.4.0 5 / 1
0.3.0 5 / 1

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.8.2

1 finding
LOW No provenance attestation provenance

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

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

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.