@dxos/protobuf-compiler MIT 32 versions

@dxos/protobuf-compiler

npm

## Installation

32

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mykola-vrmchkdxos-botgcolottisebikap-gm2richburdonegorgripasovmarik_drzad-pyivladmeschzarconontolwittjosiah

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate CI/CD migration for the dxos org.	ai	2026/06/16
maintainer-change	maintainer-removed	AI (maintainer-change): Consistent with org-wide migration to GitHub Actions publishing; not indicative of takeover.	ai	2026/06/16
phantom-deps	phantom-dep:extensionless	AI (phantom-deps): Referenced in config files per finding; indirect usage pattern is plausible for this type of package.	ai	2026/06/16
semgrep	semgrep:dynamic-require	AI (semgrep): Loads package.json from a target path for protobuf config discovery; not arbitrary module execution.	ai	2026/05/29
phantom-deps	phantom-dep:glob	AI (phantom-deps): glob is a standard utility; likely used transitively or in config files within this build tool.	ai	2026/05/29
phantom-deps	phantom-dep:@dxos/log	AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/05/29
phantom-deps	phantom-dep:@dxos/node-std	AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/05/29

Versions (showing 32 of 32)

Version	Deps	Published
0.10.0	9 / 7	2026-07-02
0.9.0	9 / 7	2026-06-15
0.8.3	9 / 10	2025-07-03
0.8.2	9 / 10	2025-06-17
0.8.1	9 / 10	2025-04-30
0.8.0	9 / 10	2025-03-15
0.7.4	9 / 10	2024-12-19
0.7.3	9 / 10	2024-12-16
0.7.2	9 / 10	2024-12-05
0.7.1	9 / 10	2024-11-26
0.7.0	9 / 10	2024-11-21
0.6.13	9 / 8	2024-10-22
0.6.12	9 / 8	2024-10-16
0.6.11	9 / 8	2024-09-23
0.6.10	9 / 8	2024-09-18
0.6.9	9 / 8	2024-09-06
0.6.8	9 / 8	2024-09-05
0.6.7	9 / 8	2024-08-26
0.6.6	9 / 8	2024-08-22
0.6.5	9 / 8	2024-08-12
0.6.4	9 / 8	2024-08-02
0.6.3	9 / 8	2024-07-26
0.6.2	9 / 8	2024-07-16
0.6.1	9 / 9	2024-07-11
0.6.0	9 / 9	2024-07-04
0.5.8	9 / 9	2024-06-14
0.5.7	9 / 9	2024-06-12
0.5.6	9 / 9	2024-06-11
0.5.5	9 / 9	2024-05-30
0.5.4	9 / 9	2024-05-29
0.5.3	9 / 9	2024-05-28
0.5.2	9 / 9	2024-05-17

v0.10.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.13

1 finding

LOW No provenance attestation provenance

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

v0.6.12

1 finding

LOW No provenance attestation provenance

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

v0.6.11

1 finding

LOW No provenance attestation provenance

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

v0.6.10

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.

v0.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

1 finding

LOW No provenance attestation provenance

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

v0.6.6

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

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.