← Home

@nxtedition/types

npm

TypeScript types to be shared between nxtedition packages.

33
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

qtodennxtadminronaggulpfniklaspanderssonolzzonhaasngnzphillipjacobdwyfldeadbeef84tobiasandersen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/records/validate/assert-guard.js AI (source-diff): typia compile-time generated validator; long lines are inlined type-check branches, not obfuscation. ai
source-diff obfuscated-file:dist/records/validate/assert.js AI (source-diff): typia compile-time generated validator; same pattern as assert-guard.js. ai
source-diff obfuscated-file:dist/records/validate/is.js AI (source-diff): typia compile-time generated validator; long lines are inlined type-check branches. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): lodash is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@types/lodash AI (phantom-deps): @types/lodash is a type-only dep; not directly imported at runtime by design. ai

Versions (showing 33 of 33)

Version Deps Published
23.1.25 4 / 12
23.1.24 6 / 12
23.1.23 6 / 12
23.1.22 6 / 12
23.1.21 6 / 12
23.1.20 6 / 12
23.1.15 6 / 12
23.1.14 6 / 12
23.0.57 6 / 13
23.0.24 3 / 9
23.0.23 3 / 9
23.0.22 3 / 9
23.0.21 3 / 9
23.0.20 3 / 9
23.0.19 3 / 9
23.0.18 3 / 9
23.0.17 3 / 9
23.0.16 3 / 9
23.0.15 3 / 9
23.0.14 3 / 9
23.0.13 3 / 9
23.0.12 3 / 9
23.0.11 3 / 9
23.0.10 3 / 9
23.0.9 3 / 9
23.0.8 3 / 9
23.0.7 3 / 8
23.0.6 3 / 8
23.0.5 3 / 8
23.0.4 3 / 8
23.0.3 3 / 8
23.0.2 3 / 8
23.0.1 3 / 7

v23.1.25

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gnz → ronag (on 2026-07-23, known maintainer) provenance

This version was published by a different npm account (ronag) than the most recent previously approved version (gnz) on 2026-07-23, but ronag is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.1.24

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dwyfl → gnz (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (gnz) than the most recent previously approved version (dwyfl) on 2026-07-09, but gnz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.1.23

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: qtoden → dwyfl (on 2026-07-03, known maintainer) provenance

This version was published by a different npm account (dwyfl) than the most recent previously approved version (qtoden) on 2026-07-03, but dwyfl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.1.22

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gulpf → qtoden (on 2026-07-01, known maintainer) provenance

This version was published by a different npm account (qtoden) than the most recent previously approved version (gulpf) on 2026-07-01, but qtoden is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.0.57

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ronag → qtoden (on 2025-11-05, known maintainer) provenance

This version was published by a different npm account (qtoden) than the most recent previously approved version (ronag) on 2025-11-05, but qtoden is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.0.22

1 finding
LOW No provenance attestation provenance

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

v23.0.21

1 finding
LOW No provenance attestation provenance

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

v23.0.20

1 finding
LOW No provenance attestation provenance

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

v23.0.19

1 finding
LOW No provenance attestation provenance

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

v23.0.18

1 finding
LOW No provenance attestation provenance

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

v23.0.17

1 finding
LOW No provenance attestation provenance

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

v23.0.16

1 finding
LOW No provenance attestation provenance

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

v23.0.15

1 finding
LOW No provenance attestation provenance

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

v23.0.14

1 finding
LOW No provenance attestation provenance

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

v23.0.13

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ronag → qtoden (on 2025-03-24, known maintainer) provenance

This version was published by a different npm account (qtoden) than the most recent previously approved version (ronag) on 2025-03-24, but qtoden is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.0.12

1 finding
LOW No provenance attestation provenance

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

v23.0.11

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: qtoden → ronag (on 2025-03-03, known maintainer) provenance

This version was published by a different npm account (ronag) than the most recent previously approved version (qtoden) on 2025-03-03, but ronag is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.0.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: qtoden → ronag (on 2025-02-24, known maintainer) provenance

This version was published by a different npm account (ronag) than the most recent previously approved version (qtoden) on 2025-02-24, but ronag is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v23.0.9

1 finding
LOW No provenance attestation provenance

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

v23.0.8

1 finding
LOW No provenance attestation provenance

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

v23.0.7

1 finding
LOW No provenance attestation provenance

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

v23.0.6

1 finding
LOW No provenance attestation provenance

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

v23.0.5

1 finding
LOW No provenance attestation provenance

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

v23.0.4

1 finding
LOW No provenance attestation provenance

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

v23.0.3

1 finding
LOW No provenance attestation provenance

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

v23.0.2

1 finding
LOW No provenance attestation provenance

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

v23.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.