webapi-parser
WebApi Parser
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Manual publish consistent with this package's history; no attestation lineage to regress. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv referenced in config files; stable FP for this package. | ai |
v0.5.0
2 findingsMaintainer email '[email protected]' uses domain 'ramses.tech' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
2 findingsMaintainer email '[email protected]' uses domain 'ramses.tech' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsMaintainer email '[email protected]' uses domain 'ramses.tech' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
2 findingsMaintainer email '[email protected]' uses domain 'ramses.tech' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.