@swagger-api/apidom-parser-adapter-yaml-1-2
Parser adapter for parsing YAML documents into base namespace.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tree-sitter-grammars/tree-sitter-yaml | AI (dependencies): Legitimate tree-sitter YAML grammar; expected dependency for a YAML parser adapter. | ai | |
| provenance | no-provenance | AI (provenance): swagger-api org consistently publishes without Sigstore provenance; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@types/ramda | AI (phantom-deps): Type-only package used as a type dependency in a TypeScript monorepo; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@tree-sitter-grammars/tree-sitter-yaml | AI (phantom-deps): Referenced in config/wasm build artifacts rather than direct JS imports; stable pattern for tree-sitter grammar packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.11.2 | 10 / 1 | |
| 1.11.1 | 10 / 1 | |
| 1.11.0 | 10 / 1 | |
| 1.10.2 | 10 / 1 | |
| 1.10.1 | 10 / 1 | |
| 1.10.0 | 10 / 1 | |
| 1.9.0 | 10 / 1 | |
| 1.8.0 | 10 / 1 | |
| 1.7.0 | 10 / 1 | |
| 1.6.0 | 10 / 1 | |
| 1.5.1 | 10 / 1 | |
| 1.5.0 | 10 / 1 | |
| 1.4.0 | 10 / 1 | |
| 1.3.0 | 10 / 1 | |
| 1.2.2 | 10 / 1 | |
| 1.2.1 | 10 / 1 | |
| 1.2.0 | 10 / 1 | |
| 1.1.0 | 10 / 1 | |
| 1.0.2 | 10 / 1 | |
| 1.0.1 | 10 / 1 | |
| 1.0.0 | 10 / 1 |
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.