@514labs/moose-proto
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Runs a workspace-local safety check script via relative path; no network access or arbitrary execution. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is expected for internal proto packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer luciofranco added alongside CI transition; consistent with legitimate org-level change for established package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher with SLSA provenance; consistent with automated release pipeline for this established package. | ai | |
| dependencies | unvetted-dep:@bufbuild/buf | AI (dependencies): @bufbuild/buf is the official Buf CLI for protobuf generation — a well-known legitimate tool. This finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@bufbuild/buf | AI (phantom-deps): @bufbuild/buf is used as a CLI tool in the gen script (not imported as a module). This pattern is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is used as a CLI tool in the gen script (not imported as a module). This pattern is expected and stable for this package. | ai |
Versions (showing 100 of 696)
| Version | Deps | Published |
|---|---|---|
| 0.6.123 | 3 / 2 | |
| 0.6.122 | 3 / 2 | |
| 0.6.121 | 3 / 2 | |
| 0.6.120 | 3 / 2 | |
| 0.6.118 | 3 / 2 | |
| 0.6.117 | 3 / 2 | |
| 0.6.116 | 3 / 2 | |
| 0.6.115 | 3 / 2 | |
| 0.6.114 | 3 / 2 | |
| 0.6.113 | 3 / 2 | |
| 0.6.110 | 3 / 2 | |
| 0.6.106 | 3 / 2 | |
| 0.6.105 | 3 / 2 | |
| 0.6.104 | 3 / 2 | |
| 0.6.103 | 3 / 2 | |
| 0.6.102 | 3 / 2 | |
| 0.6.99 | 3 / 2 | |
| 0.6.97 | 3 / 2 | |
| 0.6.96 | 3 / 2 | |
| 0.6.94 | 3 / 2 | |
| 0.6.89 | 3 / 2 | |
| 0.6.87 | 3 / 2 | |
| 0.6.80 | 3 / 2 | |
| 0.6.79 | 3 / 2 | |
| 0.6.78 | 3 / 2 | |
| 0.6.66 | 3 / 2 | |
| 0.6.65 | 3 / 2 | |
| 0.6.60 | 3 / 2 | |
| 0.6.59 | 3 / 2 | |
| 0.6.56 | 3 / 2 | |
| 0.6.54 | 3 / 2 | |
| 0.6.53 | 3 / 2 | |
| 0.6.52 | 3 / 2 | |
| 0.6.51 | 3 / 2 | |
| 0.6.49 | 3 / 2 | |
| 0.6.48 | 3 / 2 | |
| 0.6.47 | 3 / 2 | |
| 0.6.46 | 3 / 2 | |
| 0.6.45 | 3 / 2 | |
| 0.6.44 | 3 / 2 | |
| 0.6.42 | 3 / 2 | |
| 0.6.40 | 3 / 2 | |
| 0.6.39 | 3 / 2 | |
| 0.6.38 | 3 / 2 | |
| 0.6.36 | 3 / 2 | |
| 0.6.35 | 3 / 2 | |
| 0.6.34 | 3 / 2 | |
| 0.6.32 | 3 / 2 | |
| 0.6.31 | 3 / 2 | |
| 0.6.30 | 3 / 2 | |
| 0.6.29 | 3 / 2 | |
| 0.6.28 | 3 / 2 | |
| 0.6.27 | 3 / 2 | |
| 0.6.26 | 3 / 2 | |
| 0.6.25 | 3 / 2 | |
| 0.6.24 | 3 / 2 | |
| 0.6.23 | 3 / 2 | |
| 0.6.22 | 3 / 2 | |
| 0.6.21 | 3 / 2 | |
| 0.6.20 | 3 / 2 | |
| 0.6.19 | 3 / 2 | |
| 0.6.18 | 3 / 2 | |
| 0.6.17 | 3 / 2 | |
| 0.6.16 | 3 / 2 | |
| 0.6.15 | 3 / 2 | |
| 0.6.14 | 3 / 2 | |
| 0.6.13 | 3 / 2 | |
| 0.6.12 | 3 / 2 | |
| 0.6.11 | 3 / 2 | |
| 0.6.10 | 3 / 2 | |
| 0.6.9 | 3 / 2 | |
| 0.6.8 | 3 / 2 | |
| 0.6.7 | 3 / 2 | |
| 0.6.6 | 3 / 2 | |
| 0.6.5 | 3 / 2 | |
| 0.6.4 | 3 / 2 | |
| 0.6.3 | 3 / 2 | |
| 0.6.2 | 3 / 2 | |
| 0.6.1 | 3 / 2 | |
| 0.6.0 | 3 / 2 | |
| 0.5.29 | 3 / 2 | |
| 0.5.28 | 3 / 2 | |
| 0.5.27 | 3 / 2 | |
| 0.5.26 | 3 / 2 | |
| 0.5.25 | 3 / 2 | |
| 0.5.24 | 3 / 2 | |
| 0.5.23 | 3 / 2 | |
| 0.5.22 | 3 / 2 | |
| 0.5.21 | 3 / 2 | |
| 0.5.20 | 3 / 2 | |
| 0.5.19 | 3 / 2 | |
| 0.5.18 | 3 / 2 | |
| 0.5.17 | 3 / 2 | |
| 0.5.16 | 3 / 2 | |
| 0.5.15 | 3 / 2 | |
| 0.5.14 | 3 / 2 | |
| 0.5.13 | 3 / 2 | |
| 0.5.12 | 3 / 2 | |
| 0.5.11 | 3 / 2 | |
| 0.5.10 | 3 / 2 |
v0.6.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.66
2 findingsScript: node ../../scripts/ensure-safe-check.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.