← Home

@contrail/sdk

npm Homepage
100
Versions
—
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-kozdanielurchukethan-vibeiqsushantchhetryvibeiqnatevibenwilde-vibeiqashutoshvibeiqraghuvibeiq

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@nestjs/common AI (phantom-deps): Likely used via TS types/decorators not caught by import scan; established dep. ai
provenance publisher-changed AI (provenance): Move to GitHub Actions CI publishing for this org's SDK; stable across future versions. ai
dependencies unvetted-dep:@contrail/cache AI (dependencies): First-party @contrail scoped sibling package, same publisher/monorepo. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are same-org first-party packages, not third-party additions. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are org colleagues; publisher matched known prior maintainer. ai
source-diff obfuscated-file:docs/assets/main.js AI (source-diff): Typedoc-generated docs bundle (lunr search), not injected obfuscation. ai
source-diff obfuscated-file:docs/assets/search.js AI (source-diff): Typedoc-generated search index/bundle, matches generate-docs script. ai
phantom-deps phantom-dep:@contrail/util AI (phantom-deps): Same-org dependency; likely used transitively or in config rather than direct import. ai
phantom-deps phantom-dep:es6-promisify AI (phantom-deps): Declared in package.json dependencies; likely used indirectly or in config files, stable false positive for this package. ai

Versions (showing 100 of 255)

Version Deps Published
1.1.15 9 / 8
1.1.14 9 / 8
1.1.13 9 / 8
1.1.12 9 / 8
1.1.11 9 / 8
1.1.10 9 / 8
1.1.8 9 / 8
1.1.4 9 / 8
1.1.3 9 / 8
1.1.2 9 / 8
1.1.1 9 / 8
1.1.0 9 / 8
1.0.162 9 / 8
1.0.161 9 / 8
1.0.160 9 / 8
1.0.159 9 / 8
1.0.158 9 / 8
1.0.157 9 / 8
1.0.156 9 / 8
1.0.155 9 / 8
1.0.154 9 / 8
1.0.153 8 / 8
1.0.152 10 / 8
1.0.148 8 / 8
1.0.138 8 / 8
1.0.137 8 / 8
1.0.134 8 / 8
1.0.133 9 / 8
1.0.132 9 / 8
1.0.131 6 / 8
1.0.130 6 / 8
1.0.129 6 / 8
1.0.128 6 / 8
1.0.127 6 / 8
1.0.126 6 / 8
1.0.125 5 / 8
1.0.124 6 / 8
1.0.123 6 / 8
1.0.122 7 / 8
1.0.121 7 / 8
1.0.120 7 / 8
1.0.119 7 / 8
1.0.118 7 / 8
1.0.117 7 / 8
1.0.116 7 / 8
1.0.115 6 / 8
1.0.114 6 / 8
1.0.113 6 / 8
1.0.112 5 / 8
1.0.111 5 / 8
1.0.110 5 / 8
1.0.109 5 / 8
1.0.108 5 / 8
1.0.107 5 / 8
1.0.106 5 / 8
1.0.104 5 / 8
1.0.103 5 / 8
1.0.102 5 / 8
1.0.101 5 / 8
1.0.100 5 / 8
1.0.99 5 / 8
1.0.98 5 / 8
1.0.97 5 / 8
1.0.96 5 / 8
1.0.95 5 / 8
1.0.94 5 / 8
1.0.93 5 / 8
1.0.92 5 / 8
1.0.91 5 / 8
1.0.90 5 / 8
1.0.89 5 / 8
1.0.88 5 / 8
1.0.87 5 / 8
1.0.86 5 / 8
1.0.85 5 / 8
1.0.84 5 / 8
1.0.83 5 / 8
1.0.82 5 / 8
1.0.81 5 / 8
1.0.80 5 / 8
1.0.79 5 / 8
1.0.78 5 / 8
1.0.77 5 / 8
1.0.76 5 / 8
1.0.75 5 / 8
1.0.74 5 / 8
1.0.73 5 / 8
1.0.72 4 / 8
1.0.71 3 / 8
1.0.70 3 / 8
1.0.69 3 / 8
1.0.68 3 / 8
1.0.67 3 / 8
1.0.66 3 / 8
1.0.65 3 / 8
1.0.64 4 / 8
1.0.63 2 / 8
1.0.62 2 / 8
1.0.61 2 / 8
1.0.60 2 / 8
Showing 100 of 255 Next page →

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

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 → brian.lindauer (on 2022-11-12, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (kamalvibeiq) on 2022-11-12, but brian.lindauer 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.8

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

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 2022-10-25, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.0.161

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 2022-10-06, known maintainer) provenance

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

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 2022-09-30, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (kamalvibeiq) on 2022-09-30, 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.159

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: brian.lindauer → kamalvibeiq (on 2022-09-27, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (brian.lindauer) on 2022-09-27, 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.158

1 finding
LOW No provenance attestation provenance

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

v1.0.157

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: brian.lindauer → kamalvibeiq (on 2022-09-27, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (brian.lindauer) on 2022-09-27, 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.156

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: brian.lindauer → btosadoprater (on 2022-09-21, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2022-09-21, 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.155

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 → brian.lindauer (on 2022-09-14, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2022-09-14, but brian.lindauer 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.154

1 finding
LOW No provenance attestation provenance

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

v1.0.153

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: brian.lindauer → btosadoprater (on 2022-09-12, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2022-09-12, 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.152

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: brian.lindauer → btosadoprater (on 2022-09-08, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2022-09-08, 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.148

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: btosadoprater.

LOW No provenance attestation provenance

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

INFO Publisher changed: brian.lindauer → btosadoprater (on 2022-07-18, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2022-07-18, 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.138

1 finding
LOW No provenance attestation provenance

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

v1.0.137

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 → brian.lindauer (on 2022-07-08, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2022-07-08, but brian.lindauer 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.134

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 2022-06-27, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (btosadoprater) on 2022-06-27, 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.133

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 2022-06-27, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (btosadoprater) on 2022-06-27, 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.132

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 2022-06-27, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (btosadoprater) on 2022-06-27, 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.131

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: chris_vibeiq → btosadoprater (on 2022-05-18, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (chris_vibeiq) on 2022-05-18, 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.130

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 → chris_vibeiq (on 2022-05-13, known maintainer) provenance

This version was published by a different npm account (chris_vibeiq) than the most recent previously approved version (kamalvibeiq) on 2022-05-13, but chris_vibeiq 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.129

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: brian.lindauer → kamalvibeiq (on 2022-04-30, known maintainer) provenance

This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (brian.lindauer) on 2022-04-30, 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.128

1 finding
LOW No provenance attestation provenance

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

v1.0.127

1 finding
LOW No provenance attestation provenance

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

v1.0.126

1 finding
LOW No provenance attestation provenance

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

v1.0.125

1 finding
LOW No provenance attestation provenance

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

v1.0.124

1 finding
LOW No provenance attestation provenance

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

v1.0.123

1 finding
LOW No provenance attestation provenance

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

v1.0.122

1 finding
LOW No provenance attestation provenance

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

v1.0.121

1 finding
LOW No provenance attestation provenance

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

v1.0.120

1 finding
LOW No provenance attestation provenance

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

v1.0.119

1 finding
LOW No provenance attestation provenance

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

v1.0.118

1 finding
LOW No provenance attestation provenance

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

v1.0.117

1 finding
LOW No provenance attestation provenance

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

v1.0.116

1 finding
LOW No provenance attestation provenance

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

v1.0.115

1 finding
LOW No provenance attestation provenance

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

v1.0.114

1 finding
LOW No provenance attestation provenance

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

v1.0.113

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 → brian.lindauer (on 2022-03-28, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2022-03-28, but brian.lindauer 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.112

1 finding
LOW No provenance attestation provenance

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

v1.0.111

1 finding
LOW No provenance attestation provenance

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

v1.0.110

1 finding
LOW No provenance attestation provenance

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

v1.0.109

1 finding
LOW No provenance attestation provenance

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

v1.0.108

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 2022-01-26, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.0.106

1 finding
LOW No provenance attestation provenance

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

v1.0.104

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 2022-01-19, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.0.102

1 finding
LOW No provenance attestation provenance

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

v1.0.101

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: brian.lindauer → btosadoprater (on 2022-01-06, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2022-01-06, 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.100

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 → brian.lindauer (on 2022-01-06, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2022-01-06, but brian.lindauer 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.99

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: brian.lindauer → btosadoprater (on 2022-01-05, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2022-01-05, 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.98

1 finding
LOW No provenance attestation provenance

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

v1.0.97

1 finding
LOW No provenance attestation provenance

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

v1.0.96

1 finding
LOW No provenance attestation provenance

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

v1.0.95

1 finding
LOW No provenance attestation provenance

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

v1.0.94

1 finding
LOW No provenance attestation provenance

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

v1.0.93

1 finding
LOW No provenance attestation provenance

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

v1.0.92

1 finding
LOW No provenance attestation provenance

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

v1.0.91

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 → brian.lindauer (on 2021-11-12, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2021-11-12, but brian.lindauer 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.90

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 → brian.lindauer (on 2021-11-06, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2021-11-06, but brian.lindauer 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.89

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: brian.lindauer → btosadoprater (on 2021-11-02, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2021-11-02, 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.88

1 finding
LOW No provenance attestation provenance

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

v1.0.87

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 → brian.lindauer (on 2021-07-07, known maintainer) provenance

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

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 → brian.lindauer (on 2021-06-23, known maintainer) provenance

This version was published by a different npm account (brian.lindauer) than the most recent previously approved version (btosadoprater) on 2021-06-23, but brian.lindauer 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.85

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: brian.lindauer → btosadoprater (on 2021-06-22, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2021-06-22, 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.84

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: brian.lindauer → btosadoprater (on 2021-06-22, known maintainer) provenance

This version was published by a different npm account (btosadoprater) than the most recent previously approved version (brian.lindauer) on 2021-06-22, 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.83

1 finding
LOW No provenance attestation provenance

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

v1.0.82

1 finding
LOW No provenance attestation provenance

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

v1.0.81

1 finding
LOW No provenance attestation provenance

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

v1.0.80

1 finding
LOW No provenance attestation provenance

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

v1.0.79

1 finding
LOW No provenance attestation provenance

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

v1.0.78

1 finding
LOW No provenance attestation provenance

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

v1.0.77

1 finding
LOW No provenance attestation provenance

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

v1.0.76

1 finding
LOW No provenance attestation provenance

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

v1.0.75

1 finding
LOW No provenance attestation provenance

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

v1.0.74

1 finding
LOW No provenance attestation provenance

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

v1.0.73

1 finding
LOW No provenance attestation provenance

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

v1.0.72

1 finding
LOW No provenance attestation provenance

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

v1.0.71

1 finding
LOW No provenance attestation provenance

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

v1.0.70

1 finding
LOW No provenance attestation provenance

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

v1.0.69

1 finding
LOW No provenance attestation provenance

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

v1.0.68

1 finding
LOW No provenance attestation provenance

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

v1.0.67

1 finding
LOW No provenance attestation provenance

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

v1.0.66

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.