Skip to main content

Security report for osp.kitchen

Open Source Publishing · Other · N/a

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

50/100

Risk levelMedium

0–100, higher is better. How it is calculated

Open Source Publishing (OSP) operates a niche platform dedicated to open source publishing projects, emphasizing copyleft principles and collaborative cultural work. The website presents a variety of projects, tools, workshops, and research initiatives, targeting artists, cultural workers, and the open source community. The business model revolves around sharing and improving open source publishing resources and projects. Technically, the site uses legacy JavaScript libraries like jQuery 1.11.0 and standard web technologies such as CSS and SVG. The site is moderately optimized for performance and mobile use but lacks advanced accessibility and SEO features. Security posture is moderate with no visible vulnerabilities but lacks HTTPS confirmation and security headers. Privacy compliance is weak due to absence of privacy and cookie policies. No contact information or incident response details are provided, limiting trust and compliance. WHOIS data is unavailable due to TLD restrictions and privacy protection, but the domain is actively maintained. Overall, the site is functional and content-rich but requires improvements in security, privacy, and compliance to enhance trust and professionalism.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

8 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching osp.kitchen

This scan found 25 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
52
Security headers
15
Email security
70
DNS health
75
Network security
40
GDPR outside view
50
Average
50

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

OSP holds a unique position in the open source publishing niche, offering tools, workshops, and research to a specialized audience. Its competitive advantage lies in transparency and copyleft licensing, fostering community collaboration. Revenue streams are unclear but likely non-commercial or grant-based given the open source ethos. The partnership ecosystem includes references to cultural institutions like iMAL. Growth indicators include recent project updates and active blog posts. The business operates on a small scale with a focused community presence.

Security posture

The website demonstrates a basic security maturity level with no evident vulnerabilities or exposed sensitive data. However, the absence of HTTPS confirmation and security headers is a significant gap. The use of an outdated jQuery version may expose the site to known vulnerabilities. Lack of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. Incident response readiness is not evident due to missing contact channels for security issues. Overall, the security posture is moderate but requires enhancements to meet best practices and regulatory requirements.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate and enforce secure connections site-wide.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and inform users.
  3. Upgrade JavaScript libraries, especially jQuery, to current secure versions.
  4. Publish clear contact information including security incident response contacts.
  5. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Open Source Publishing
Description
Open Source Publishing (OSP) is a platform focused on publishing projects with an open source philosophy. It offers tools, foundry, workshops, research, and live projects related to open source publishing. The site encourages studying, improving, redistributing, and releasing improvements under copyleft principles.
Key services
Publishing tools, Workshops, Foundry (likely font or design related), Research projects, Live projects, Blog content
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.11.0, JavaScript, CSS, SVG
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries detected

Analytics and tracking

Services
StatCounter
Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
StatCounter
Tracking pixels
StatCounter
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is fully accessible with rich content and active project updates.
  2. No privacy, cookie, or terms of service policies found, which is a compliance gap.
  3. No explicit contact emails or phone numbers found on the site.
  4. WHOIS data is unavailable due to TLD restrictions and privacy protection.
  5. Uses older jQuery version which may pose security risks.
  6. Includes a newsletter subscription form collecting email addresses.
  7. External links mostly point to reputable domains like Wikipedia and project-related blogs.
  8. No social media links detected.
  9. No security headers or HTTPS status visible from provided data.
  10. Uses StatCounter for analytics and tracking.
Technical notes

Notes

The website uses basic web technologies including jQuery 1.11.0, CSS, and SVG graphics. The HTML structure is valid but lacks modern frameworks or CMS indications. Performance is moderate with some mobile optimization but limited accessibility features. SEO is basic with minimal meta tags and no structured data like JSON-LD or Open Graph tags detected. Hosting provider and CMS are not identifiable from the data. The site uses StatCounter for analytics, indicating minimal user tracking. Technical debt includes outdated libraries and missing security best practices.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with osp.kitchen. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review osp.kitchen.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.