@asyncapi/parser
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): asyncapi/parser-js uses GitHub Actions CI for publishing; bot→GHA transition is expected and backed by SLSA attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established AsyncAPI org package with SLSA provenance; dormancy reflects release cadence, not account takeover. | ai | |
| phantom-deps | phantom-dep:avsc | AI (phantom-deps): avsc is a legitimate runtime dep for Avro schema parsing; phantom detection likely misses convention-based or indirect imports. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): TypeScript type definition package loaded by convention; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/urijs | AI (phantom-deps): TypeScript type definition package loaded by convention; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): js-yaml is a standard YAML parsing dep for an AsyncAPI parser; phantom detection likely misses indirect usage paths. | ai | |
| phantom-deps | phantom-dep:@openapi-contrib/openapi-schema-to-json-schema | AI (phantom-deps): Legitimate OpenAPI-to-JSON-Schema conversion dep; phantom detection likely misses config-driven or indirect imports. | ai | |
| dependencies | unvetted-dep:@stoplight/json | AI (dependencies): @stoplight/json is a well-known utility from Stoplight; legitimate dependency for JSON parsing/validation. | ai | |
| dependencies | unvetted-dep:@stoplight/types | AI (dependencies): @stoplight/types is a well-known types package from Stoplight; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-core | AI (dependencies): @stoplight/spectral-core is the core of the well-known Spectral linting framework; legitimate dependency for spec validation. | ai | |
| dependencies | unvetted-dep:@stoplight/json-ref-readers | AI (dependencies): Legitimate Stoplight package for JSON reference resolution; expected in a spec parser. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-parsers | AI (dependencies): Legitimate Stoplight Spectral package; expected dependency for spec parsing. | ai | |
| typosquat | typosquat.levenshtein:parcel | AI (typosquat): @asyncapi/parser is the official AsyncAPI spec parser under the @asyncapi org scope — not a typosquat of 'parcel'. Levenshtein match is a false positive; stable across all versions. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-functions | AI (dependencies): Legitimate Stoplight Spectral package; expected dependency for spec validation functions. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-ref-resolver | AI (dependencies): Legitimate Stoplight Spectral package; expected dependency for reference resolution. | ai | |
| dependencies | unvetted-dep:@openapi-contrib/openapi-schema-to-json-schema | AI (dependencies): Legitimate OpenAPI Contrib package for schema conversion; expected in an AsyncAPI parser that supports OpenAPI schemas. | ai | |
| dependencies | unvetted-dep:@stoplight/json-ref-resolver | AI (dependencies): Legitimate Stoplight package for JSON reference resolution; expected in a spec parser. | ai | |
| dependencies | unvetted-dep:@types/urijs | AI (dependencies): @types/urijs is a legitimate DefinitelyTyped package; expected TypeScript type dependency for this parser. | ai | |
| dependencies | unvetted-dep:@asyncapi/specs | AI (dependencies): @asyncapi/specs is the official AsyncAPI specification package from the same organization; core dependency for this parser. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 19 / 27 | |
| 3.5.0 | 19 / 27 | |
| 3.4.0 | 19 / 27 | |
| 3.3.0 | 19 / 27 | |
| 3.2.2 | 19 / 27 | |
| 3.2.1 | 19 / 27 | |
| 3.2.0 | 19 / 27 | |
| 3.1.0 | 19 / 28 | |
| 3.0.16 | 19 / 28 | |
| 3.0.15 | 19 / 28 | |
| 3.0.14 | 19 / 28 | |
| 3.0.13 | 19 / 28 | |
| 3.0.12 | 19 / 28 | |
| 3.0.11 | 19 / 28 | |
| 3.0.10 | 19 / 28 | |
| 3.0.9 | 19 / 28 | |
| 3.0.8 | 19 / 28 | |
| 3.0.7 | 19 / 28 | |
| 3.0.6 | 19 / 28 | |
| 3.0.5 | 19 / 28 | |
| 3.0.4 | 19 / 28 | |
| 3.0.3 | 19 / 28 | |
| 3.0.2 | 19 / 28 | |
| 3.0.1 | 19 / 28 | |
| 3.0.0 | 19 / 28 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.