@doquflow/server
Docuflow MCP server — lets AI agents read codebases and persist living specs
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): @doquflow/server is a scoped MCP server package; no functional or naming relationship to semver. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 1 / 3 | |
| 1.6.0 | 1 / 3 | |
| 1.5.1 | 1 / 2 | |
| 1.5.0 | 1 / 2 | |
| 1.3.0 | 1 / 2 | |
| 1.1.1 | 1 / 2 | |
| 0.5.5 | 1 / 2 | |
| 0.5.3 | 1 / 2 | |
| 0.5.2 | 1 / 2 | |
| 0.5.1 | 1 / 2 | |
| 0.4.6 | 1 / 2 | |
| 0.4.2 | 1 / 2 | |
| 0.4.1 | 1 / 2 | |
| 0.3.0 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.0 | 1 / 2 |
v1.7.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.
v1.6.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.
v1.5.1
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.
v1.5.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.
v1.3.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.
v1.1.1
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.5.5
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.5.3
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.5.2
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.5.1
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.6
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.2
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.1
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.2.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.1.0
3 findingsPackage name '@doquflow/server' is 1 edit(s) away from popular package 'semver'.
Maintainer email '[email protected]' uses domain 'doquflows.dev' 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.