← Home

@contrail/util

npm

General JavaScript utilities

51
Versions
ISC
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

grant.hallbrian.lindauercfvibeiqbtosadopraterchris_vibeiqzileevamattvitellomazairajprashantvibeiqkartikisahuadamvibeiqzachsibert_vibeiqjaime-vibeiqmelba.lewisricardojsiscolrakeshvibeiqvadim-kozdanielurchuknwilde-vibeiqashutoshvibeiqraghuvibeiq

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Publisher is a known prior maintainer, not a takeover. ai
dependencies unvetted-dep:dynamodb-data-types AI (dependencies): Legitimate AWS DynamoDB helper lib, consistent with package's AWS utility purpose. ai
maintainer-change maintainer-added AI (maintainer-change): Publisher is a known prior maintainer with strong track record; looks like org reshuffle. ai
bogus-package bogus-package AI (bogus-package): Long-standing internal utility package, sparse metadata is stable pattern not spam. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped package @contrail/util is an established utility in the contrail namespace; no relation to uuid. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is part of a legitimate decompression pipeline (base64 → fflate), not payload execution. ai

Versions (showing 51 of 88)

View all versions
Version Deps Published
1.3.1 3 / 8
1.3.0 3 / 8
1.2.1 4 / 8
1.2.0 3 / 8
1.1.19 3 / 8
1.1.18 3 / 8
1.1.17 3 / 8
1.1.16 3 / 8
1.1.15 3 / 8
1.1.14 3 / 8
1.1.13 3 / 8
1.1.12 3 / 7
1.1.11 3 / 7
1.1.10 3 / 7
1.1.9 3 / 7
1.1.8 3 / 7
1.1.7 3 / 7
1.1.6 3 / 7
1.1.5 2 / 7
1.1.4 2 / 7
1.1.3 2 / 7
1.1.2 2 / 7
1.1.1 2 / 7
1.1.0 2 / 7
1.0.65 2 / 7
1.0.64 2 / 7
1.0.63 2 / 7
1.0.62 2 / 7
1.0.61 2 / 7
1.0.60 2 / 7
1.0.59 2 / 7
1.0.58 1 / 7
1.0.57 1 / 7
1.0.56 1 / 7
1.0.55 1 / 7
1.0.53 3 / 7
1.0.52 3 / 7
1.0.51 3 / 7
1.0.50 1 / 7
1.0.49 1 / 7
1.0.48 1 / 7
1.0.47 1 / 7
1.0.46 1 / 7
1.0.45 1 / 7
1.0.44 1 / 7
1.0.43 1 / 7
1.0.42 0 / 7
1.0.41 0 / 7
1.0.40 0 / 7
1.0.39 0 / 7
1.0.38 0 / 7

v1.1.19

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: btosadoprater → adamvibeiq (on 2025-09-18, known maintainer) provenance

This version was published by a different npm account (adamvibeiq) than the most recent previously approved version (btosadoprater) on 2025-09-18, but adamvibeiq 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.

v1.1.18

1 finding
LOW No provenance attestation provenance

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

v1.1.17

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: prashantvibeiq → btosadoprater (on 2025-09-15, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (prashantvibeiq) on 2025-09-15, but btosadoprater 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.

v1.1.16

1 finding
LOW No provenance attestation provenance

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

v1.1.15

1 finding
LOW No provenance attestation provenance

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

v1.1.14

1 finding
LOW No provenance attestation provenance

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

v1.1.13

1 finding
LOW No provenance attestation provenance

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

v1.1.12

1 finding
LOW No provenance attestation provenance

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

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.10

1 finding
LOW No provenance attestation provenance

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

v1.1.9

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: prashantvibeiq → adamvibeiq (on 2025-05-16, known maintainer) provenance

This version was published by a different npm account (adamvibeiq) than the most recent previously approved version (prashantvibeiq) on 2025-05-16, but adamvibeiq 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.

v1.1.4

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: btosadoprater → prashantvibeiq (on 2025-04-10, known maintainer) provenance

This version was published by a different npm account (prashantvibeiq) than the most recent previously approved version (btosadoprater) on 2025-04-10, but prashantvibeiq 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.

v1.1.3

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: mattvitello → btosadoprater (on 2025-03-25, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (mattvitello) on 2025-03-25, but btosadoprater 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.

v1.1.2

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: prashantvibeiq → mattvitello (on 2025-03-14, known maintainer) provenance

This version was published by a different npm account (mattvitello) than the most recent previously approved version (prashantvibeiq) on 2025-03-14, but mattvitello 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.

v1.1.1

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: zileeva → prashantvibeiq (on 2025-02-13, known maintainer) provenance

This version was published by a different npm account (prashantvibeiq) than the most recent previously approved version (zileeva) on 2025-02-13, but prashantvibeiq 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.

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.65

1 finding
LOW No provenance attestation provenance

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

v1.0.64

1 finding
LOW No provenance attestation provenance

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

v1.0.63

1 finding
LOW No provenance attestation provenance

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

v1.0.62

1 finding
LOW No provenance attestation provenance

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

v1.0.61

1 finding
LOW No provenance attestation provenance

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

v1.0.60

1 finding
LOW No provenance attestation provenance

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

v1.0.59

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: adamvibeiq → zileeva (on 2024-11-25, known maintainer) provenance

This version was published by a different npm account (zileeva) than the most recent previously approved version (adamvibeiq) on 2024-11-25, but zileeva 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.

v1.0.58

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: adamvibeiq → zileeva (on 2024-11-25, known maintainer) provenance

This version was published by a different npm account (zileeva) than the most recent previously approved version (adamvibeiq) on 2024-11-25, but zileeva 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.

v1.0.57

1 finding
LOW No provenance attestation provenance

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

v1.0.56

1 finding
LOW No provenance attestation provenance

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

v1.0.55

1 finding
LOW No provenance attestation provenance

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

v1.0.53

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: adamvibeiq → mattvitello (on 2024-11-21, known maintainer) provenance

This version was published by a different npm account (mattvitello) than the most recent previously approved version (adamvibeiq) on 2024-11-21, but mattvitello 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.

v1.0.52

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: adamvibeiq → zileeva (on 2024-11-21, known maintainer) provenance

This version was published by a different npm account (zileeva) than the most recent previously approved version (adamvibeiq) on 2024-11-21, but zileeva 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.

v1.0.51

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: zileeva → adamvibeiq (on 2024-11-21, known maintainer) provenance

This version was published by a different npm account (adamvibeiq) than the most recent previously approved version (zileeva) on 2024-11-21, but adamvibeiq 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.

v1.0.50

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: zileeva → adamvibeiq (on 2024-11-15, known maintainer) provenance

This version was published by a different npm account (adamvibeiq) than the most recent previously approved version (zileeva) on 2024-11-15, but adamvibeiq 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.

v1.0.49

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.

v1.0.48

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.

v1.0.47

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: btosadoprater → kamalvibeiq (on 2024-01-19, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (btosadoprater) on 2024-01-19, but kamalvibeiq 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.

v1.0.46

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: mattvitello → btosadoprater (on 2023-12-07, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (mattvitello) on 2023-12-07, but btosadoprater 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.

v1.0.45

1 finding
LOW No provenance attestation provenance

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

v1.0.44

1 finding
LOW No provenance attestation provenance

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

v1.0.43

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: btosadoprater → mattvitello (on 2023-11-03, known maintainer) provenance

This version was published by a different npm account (mattvitello) than the most recent previously approved version (btosadoprater) on 2023-11-03, but mattvitello 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.

v1.0.42

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: kamalvibeiq → btosadoprater (on 2023-10-24, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (kamalvibeiq) on 2023-10-24, but btosadoprater 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.

v1.0.41

1 finding
LOW No provenance attestation provenance

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

v1.0.40

1 finding
LOW No provenance attestation provenance

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

v1.0.39

1 finding
LOW No provenance attestation provenance

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

v1.0.38

1 finding
LOW No provenance attestation provenance

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