← Home

@graphql-codegen/visitor-plugin-common

npm Repository
100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

dotansimhaardatankamilkisielaurigotheguild-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): 22 new source files are consistent with feature additions in an active monorepo; no obfuscation or bundled injection signals. ai
dependencies unvetted-dep:@graphql-toolkit/relay-operation-optimizer AI (dependencies): Part of the graphql-toolkit ecosystem, used as a replacement for relay-compiler; contextually appropriate for this GraphQL codegen plugin. ai
dependencies unvetted-dep:pascal-case AI (dependencies): pascal-case is a well-known, widely-used utility package; appropriate dependency for a code generation plugin. ai
provenance missing-githead AI (provenance): Established publisher; missing gitHead in this version is a minor provenance signal but consistent with publishing patterns from this trusted maintainer. ai
publish-pattern new-deps-added AI (publish-pattern): New dependencies are all legitimate, established packages; consistent with feature development in active monorepo. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance attestation; published in 2020-era tooling. Stable false positive for this package. ai
npm-metadata no-description AI (npm-metadata): Missing description is a metadata quirk, not a malware indicator for this established package. ai
bogus-package bogus-package AI (bogus-package): This is a monorepo sub-package from the well-known graphql-codegen project; missing description/repo/keywords in package.json is standard for build artifacts from monorepos. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit dependency pattern for TypeScript libraries; stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): theguild-bot addition reflects The Guild's standard practice of using a bot account for automated publishing; not a compromise indicator. ai
provenance publisher-changed AI (provenance): theguild-bot is The Guild's official CI publishing account; the dotansimha → theguild-bot transition is a documented, legitimate org-level change for the graphql-code-generator project. ai
dependencies unvetted-dep:@graphql-tools/relay-operation-optimizer AI (dependencies): @graphql-tools/relay-operation-optimizer is part of The Guild's graphql-tools ecosystem; legitimate dependency for relay optimization support. ai
dependencies unvetted-dep:@graphql-codegen/plugin-helpers AI (dependencies): @graphql-codegen/plugin-helpers is a sibling package in the same graphql-code-generator monorepo; expected dependency. ai
dependencies unvetted-dep:@graphql-tools/utils AI (dependencies): @graphql-tools/utils is a core package from The Guild's graphql-tools monorepo; legitimate and expected. ai
dependencies unvetted-dep:change-case-all AI (dependencies): change-case-all is a well-known string casing utility; standard dependency in graphql-codegen ecosystem. ai
dependencies unvetted-dep:parse-filepath AI (dependencies): parse-filepath is a legitimate utility package; expected dependency for path handling in graphql-codegen plugins. ai

Versions (showing 100 of 464)

Hide prereleases
Version Deps Published
1.17.9 9 / 0
1.17.8 9 / 0
1.17.7 9 / 0
1.17.6 9 / 0
1.17.5 9 / 0
1.17.4 9 / 2
1.17.3 9 / 2
1.17.1 9 / 2
1.17.0 9 / 2
1.16.3 9 / 2
1.16.2 9 / 2
1.16.1 9 / 2
1.16.0 9 / 2
1.15.4 9 / 2
1.15.3 9 / 2
1.15.2 9 / 2
1.15.1 9 / 2
1.15.0 9 / 0
1.14.0 9 / 0
1.13.5 9 / 0
1.13.4 9 / 0
1.13.3 9 / 0
1.13.2 8 / 0
1.13.1 8 / 0
1.13.0 7 / 0
1.12.2 7 / 0
1.12.1 7 / 0
1.12.0 7 / 0
1.11.2 6 / 0
1.11.1 6 / 0
1.11.0 6 / 0
1.10.0 6 / 0
1.9.1 6 / 0
1.9.0 5 / 0
1.8.3 6 / 7
1.8.2 6 / 7
1.8.1 6 / 7
1.8.0 6 / 7
1.7.0 5 / 7
1.6.1 5 / 7
1.6.0 5 / 7
1.5.0 5 / 7
1.4.0 5 / 7
1.3.1 5 / 7
1.3.0 5 / 7
1.2.1 5 / 7
1.2.0 5 / 7
1.1.3 5 / 7
1.1.1 5 / 7
1.1.0 5 / 7
1.0.7 5 / 7
1.0.6 5 / 7
1.0.5 5 / 7
1.0.4 5 / 4
1.0.3 5 / 4
1.0.2 5 / 4
1.0.1 5 / 4
1.0.0 5 / 4
7.0.0-alpha-20260422122602-fdc454ac0f4fe86baab0e0c4fa19b8ad1d249124 10 / 0
7.0.0-alpha-20260419102718-b51558732f8016c9d9f645501d1e06891d639dc4 10 / 0
7.0.0-alpha-20260418131654-503ab6a01555d0981481d105f71b7685480bcb3c 10 / 0
7.0.0-alpha-20260413135420-eb41159d047f15f84648ca3282322ef660a92d63 10 / 0
7.0.0-alpha-20260413134408-61e21f4b1b8f8b029c7078874e088f7e34608c4d 10 / 0
7.0.0-alpha-20260413134044-219e6c60eb76b7ddbddd6681ff504fcd03e97227 10 / 0
7.0.0-alpha-20260413133253-405d8586497bf3936183822bddf74940ae72abe9 10 / 0
7.0.0-alpha-20260413131710-0312d1fa627824dd432c55bb28404b073ce33830 10 / 0
7.0.0-alpha-20260413131420-7aed107788d15ef2a04c40291da32944fdae7888 10 / 0
7.0.0-alpha-20260331131036-3103b7af1f0e6f15d6cf4d9521376fa82383845e 10 / 0
7.0.0-alpha-20260331125845-e6d2a4ce6d2c1f46380441d80f8a3b827fbac6d8 10 / 0
7.0.0-alpha-20260330130133-91e5886d742ea13cf65e87b235232a6caefa6baa 10 / 0
7.0.0-alpha-20260327125229-b352e1272229b87533612b99fe96134d0c6a89bb 10 / 0
7.0.0-alpha-20260327124537-83b8ce99e4a48b057c6497cf86557bfc5f4695b3 10 / 0
7.0.0-alpha-20260327112358-664cd6b5ddb52298c1b469a72d2b2d1cc5332c5e 10 / 0
7.0.0-alpha-20260326135024-68a6e8709957a26f7d6283c9ab5e8e91c613b578 10 / 0
7.0.0-alpha-20260325030620-a34d3cfadd8fdfc90fe3e514f91664be3df538c2 10 / 0
7.0.0-alpha-20260324113123-a34d3cfadd8fdfc90fe3e514f91664be3df538c2 10 / 0
7.0.0-alpha-20260323113908-33f45bf480eca7cc9aef160da1e6e7c91c33a326 10 / 0
7.0.0-alpha-20260323113133-b4751ac0b0b9e0ea3628e41dd9b3cfc0847ea401 10 / 0
7.0.0-alpha-20260322134632-9090a8487a642360d524bf6775c5077a85b08f83 10 / 0
7.0.0-alpha-20260322133204-5412890edafd92f070ac53f10de834c087e9d96e 10 / 0
7.0.0-alpha-20260322132510-14d22072d7f8a2b88050538ae695ec8c3a7b4bce 10 / 0
7.0.0-alpha-20260322081724-67c359e4b8e2a36899a1b522f2f43daf93e97008 10 / 0
7.0.0-alpha-20260322081310-6ec1b48e1e4dc6dd34e4a08624c2fe5c1026579f 10 / 0
7.0.0-alpha-20260322080719-ae38b588aa075cb07463dfe36d85c935e6f3dfd7 10 / 0
7.0.0-alpha-20260322055836-e6ce8330ea9f427d8ca1132b23c6c7241b5a3a5f 10 / 0
7.0.0-alpha-20260322035717-ff62ae6c37a82c1ba65c814470aef10053d14fb3 10 / 0
7.0.0-alpha-20260319122931-bc62f449e4c14584c59649048f26d62a43898960 10 / 0
7.0.0-alpha-20260319120713-b6f95bb4d1195c2597e9c2e1639a7d4406c82823 10 / 0
7.0.0-alpha-20260319115642-cc52a81e5eb7d0f62a6f5c31ba1eebb5b34ef99f 10 / 0
7.0.0-alpha-20260319115552-6734f1a6e8c2b9fab70b7418e374635f0e1e539d 10 / 0
7.0.0-alpha-20260319115102-a90cdc038da5253a9e2837ce7d9991e9427ebb73 10 / 0
7.0.0-alpha-20260319114227-331877302a4efbc2f211478a904f71a2fef258ff 10 / 0
7.0.0-alpha-20260319112145-558c4a2465c7723ec5a41fc91f397dfe6aea8956 10 / 0
7.0.0-alpha-20260319095647-e7d4bd0fdf47a5a1a580391da978c956543d9854 10 / 0
7.0.0-alpha-20260318141253-1a79eada98cda15027e7df66a926a34087158d4f 10 / 0
7.0.0-alpha-20260318140537-be36bfdea1088c2b31d73c292458b8642d89835c 10 / 0
7.0.0-alpha-20260318135918-3145fdcdc944075bb16c5b3463d1f6856eee3d25 10 / 0
7.0.0-alpha-20260318134322-cdbc9b25969f8290b4888b22c8f770dfde4155de 10 / 0
7.0.0-alpha-20260316132202-81afcbeaa731b4d3dd26846af4c8a71edb50e6b0 10 / 0
7.0.0-alpha-20260316123536-f1be5d641cea639e270924f1ec243d48c90bda21 10 / 0
Showing 100 of 464 Next page →

v1.17.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.14.0

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.13.5

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.13.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.13.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.13.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.13.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.13.0

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.12.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.11.2

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.11.1

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.11.0

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.10.0

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.9.1

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.9.0

2 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: dotansimha.

LOW No provenance attestation provenance

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

v1.8.3

1 finding
LOW No provenance attestation provenance

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

v1.8.2

1 finding
LOW No provenance attestation provenance

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

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

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.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.

v7.0.0-alpha-20260422122602-fdc454ac0f4fe86baab0e0c4fa19b8ad1d249124

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260419102718-b51558732f8016c9d9f645501d1e06891d639dc4

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260418131654-503ab6a01555d0981481d105f71b7685480bcb3c

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260413135420-eb41159d047f15f84648ca3282322ef660a92d63

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260413134408-61e21f4b1b8f8b029c7078874e088f7e34608c4d

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260413134044-219e6c60eb76b7ddbddd6681ff504fcd03e97227

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260413133253-405d8586497bf3936183822bddf74940ae72abe9

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260413131710-0312d1fa627824dd432c55bb28404b073ce33830

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260413131420-7aed107788d15ef2a04c40291da32944fdae7888

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260331131036-3103b7af1f0e6f15d6cf4d9521376fa82383845e

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260331125845-e6d2a4ce6d2c1f46380441d80f8a3b827fbac6d8

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260330130133-91e5886d742ea13cf65e87b235232a6caefa6baa

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260327125229-b352e1272229b87533612b99fe96134d0c6a89bb

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260327124537-83b8ce99e4a48b057c6497cf86557bfc5f4695b3

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260327112358-664cd6b5ddb52298c1b469a72d2b2d1cc5332c5e

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260326135024-68a6e8709957a26f7d6283c9ab5e8e91c613b578

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260325030620-a34d3cfadd8fdfc90fe3e514f91664be3df538c2

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260324113123-a34d3cfadd8fdfc90fe3e514f91664be3df538c2

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260323113908-33f45bf480eca7cc9aef160da1e6e7c91c33a326

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260323113133-b4751ac0b0b9e0ea3628e41dd9b3cfc0847ea401

1 finding
INFO No provenance attestation provenance

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

v7.0.0-alpha-20260322134632-9090a8487a642360d524bf6775c5077a85b08f83

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322133204-5412890edafd92f070ac53f10de834c087e9d96e

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322132510-14d22072d7f8a2b88050538ae695ec8c3a7b4bce

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322081724-67c359e4b8e2a36899a1b522f2f43daf93e97008

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322081310-6ec1b48e1e4dc6dd34e4a08624c2fe5c1026579f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322080719-ae38b588aa075cb07463dfe36d85c935e6f3dfd7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322055836-e6ce8330ea9f427d8ca1132b23c6c7241b5a3a5f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260322035717-ff62ae6c37a82c1ba65c814470aef10053d14fb3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319122931-bc62f449e4c14584c59649048f26d62a43898960

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319120713-b6f95bb4d1195c2597e9c2e1639a7d4406c82823

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319115642-cc52a81e5eb7d0f62a6f5c31ba1eebb5b34ef99f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319115552-6734f1a6e8c2b9fab70b7418e374635f0e1e539d

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319115102-a90cdc038da5253a9e2837ce7d9991e9427ebb73

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319114227-331877302a4efbc2f211478a904f71a2fef258ff

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319112145-558c4a2465c7723ec5a41fc91f397dfe6aea8956

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260319095647-e7d4bd0fdf47a5a1a580391da978c956543d9854

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260318141253-1a79eada98cda15027e7df66a926a34087158d4f

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260318140537-be36bfdea1088c2b31d73c292458b8642d89835c

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260318135918-3145fdcdc944075bb16c5b3463d1f6856eee3d25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260318134322-cdbc9b25969f8290b4888b22c8f770dfde4155de

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260316132202-81afcbeaa731b4d3dd26846af4c8a71edb50e6b0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0-alpha-20260316123536-f1be5d641cea639e270924f1ec243d48c90bda21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.