@asyncapi/protobuf-schema-parser
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from asyncapi-bot to GitHub Actions CI with SLSA provenance; org-level CI migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI migration; established @asyncapi org package. | ai | |
| phantom-deps | phantom-dep:@types/protocol-buffers-schema | AI (phantom-deps): @types packages are type-only and loaded by TypeScript convention, not direct imports; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.8.2 | 3 / 19 | |
| 3.8.1 | 3 / 22 | |
| 3.7.0 | 3 / 22 | |
| 3.6.0 | 3 / 22 | |
| 3.5.1 | 3 / 22 | |
| 3.5.0 | 3 / 22 | |
| 3.4.1 | 3 / 22 | |
| 3.4.0 | 3 / 22 | |
| 3.3.0 | 3 / 22 | |
| 3.2.15 | 3 / 22 | |
| 3.2.14 | 3 / 22 | |
| 3.2.13 | 3 / 22 |
v3.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.