@promptbook/remote-server
Promptbook: Create persistent AI agents that turn your company's scattered knowledge into action
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Monorepo package with frequent large builds; no malicious content indicated. | ai | |
| email-domain | unclaimed-email:hejny.org | AI (email-domain): Long-standing trusted publisher; domain quirk, no hijack evidence. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are official AI SDKs matching package's LLM purpose. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Used in subprocess execution helper to pass env vars; standard pattern for this type of framework. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Buffer.from with base64 is a standard data decoding pattern, not payload hiding. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used for Node.js environment detection (global check); stable pattern across this package's versions. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Acknowledged in source with TODO comment; used for script execution in AI pipeline context. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Expected for a server-side Node.js execution framework. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard Proxy/Reflect pattern in a framework; not obfuscation. | ai |
Versions (showing 100 of 184)
| Version | Deps | Published |
|---|---|---|
| 0.112.0 | 21 / 0 | |
| 0.110.0 | 20 / 0 | |
| 0.105.0 | 19 / 0 | |
| 0.104.0 | 13 / 0 | |
| 0.103.0 | 13 / 0 | |
| 0.102.0 | 13 / 0 | |
| 0.101.0 | 12 / 0 | |
| 0.100.2 | 12 / 0 | |
| 0.100.1 | 12 / 0 | |
| 0.100.0 | 12 / 0 | |
| 0.98.0 | 13 / 0 | |
| 0.95.0 | 13 / 0 | |
| 0.94.0 | 13 / 0 | |
| 0.93.0 | 13 / 0 | |
| 0.92.0 | 13 / 0 | |
| 0.89.0 | 13 / 0 | |
| 0.88.0 | 11 / 0 | |
| 0.86.31 | 11 / 0 | |
| 0.86.30 | 11 / 0 | |
| 0.86.22 | 11 / 0 | |
| 0.86.10 | 11 / 0 | |
| 0.86.8 | 11 / 0 | |
| 0.86.6 | 11 / 0 | |
| 0.86.5 | 11 / 0 | |
| 0.85.0 | 11 / 0 | |
| 0.84.0 | 8 / 0 | |
| 0.83.0 | 8 / 0 | |
| 0.82.0 | 8 / 0 | |
| 0.81.0 | 3 / 0 | |
| 0.80.0 | 3 / 0 | |
| 0.79.0 | 3 / 0 | |
| 0.78.4 | 3 / 0 | |
| 0.78.3 | 3 / 0 | |
| 0.78.2 | 3 / 0 | |
| 0.77.1 | 3 / 0 | |
| 0.77.0 | 3 / 0 | |
| 0.76.0 | 3 / 0 | |
| 0.75.10 | 3 / 0 | |
| 0.75.9 | 3 / 0 | |
| 0.75.6 | 3 / 0 | |
| 0.75.5 | 3 / 0 | |
| 0.75.4 | 3 / 0 | |
| 0.75.3 | 3 / 0 | |
| 0.75.2 | 3 / 0 | |
| 0.75.1 | 3 / 0 | |
| 0.74.0 | 3 / 0 | |
| 0.73.0 | 3 / 0 | |
| 0.72.0 | 3 / 0 | |
| 0.69.6 | 3 / 0 | |
| 0.69.5 | 3 / 0 | |
| 0.69.3 | 3 / 0 | |
| 0.69.2 | 3 / 0 | |
| 0.69.1 | 3 / 0 | |
| 0.69.0 | 3 / 0 | |
| 0.68.5 | 3 / 0 | |
| 0.68.4 | 3 / 0 | |
| 0.68.3 | 3 / 0 | |
| 0.68.2 | 3 / 0 | |
| 0.68.0 | 3 / 0 | |
| 0.67.9 | 3 / 0 | |
| 0.67.8 | 3 / 0 | |
| 0.67.7 | 3 / 0 | |
| 0.67.6 | 3 / 0 | |
| 0.67.5 | 3 / 0 | |
| 0.67.4 | 3 / 0 | |
| 0.67.3 | 3 / 0 | |
| 0.67.2 | 3 / 0 | |
| 0.67.1 | 3 / 0 | |
| 0.67.0 | 3 / 0 | |
| 0.66.0 | 3 / 0 | |
| 0.65.0 | 7 / 0 | |
| 0.63.4 | 3 / 0 | |
| 0.63.3 | 3 / 0 | |
| 0.63.2 | 3 / 0 | |
| 0.63.1 | 3 / 0 | |
| 0.63.0 | 3 / 0 | |
| 0.62.1 | 3 / 0 | |
| 0.62.0 | 3 / 0 | |
| 0.61.0 | 3 / 0 | |
| 0.60.1 | 3 / 0 | |
| 0.60.0 | 3 / 0 | |
| 0.59.0 | 3 / 0 | |
| 0.58.0 | 3 / 0 | |
| 0.57.2 | 3 / 0 | |
| 0.57.1 | 3 / 0 | |
| 0.57.0 | 3 / 0 | |
| 0.56.0 | 3 / 0 | |
| 0.55.0 | 3 / 0 | |
| 0.54.1 | 3 / 0 | |
| 0.54.0 | 3 / 0 | |
| 0.53.0 | 3 / 0 | |
| 0.52.0 | 3 / 0 | |
| 0.51.0 | 3 / 0 | |
| 0.50.0 | 3 / 0 | |
| 0.49.1 | 3 / 0 | |
| 0.49.0 | 3 / 0 | |
| 0.48.0 | 3 / 0 | |
| 0.47.0 | 3 / 0 | |
| 0.46.0 | 3 / 0 | |
| 0.45.0 | 3 / 0 |
v0.112.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.89.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.88.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.85.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.82.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.81.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.80.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.79.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.78.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.78.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.78.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.77.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.77.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.76.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.74.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.73.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.72.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.69.6
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.69.5
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.69.3
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.69.2
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.69.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.69.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.5
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.4
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.3
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.2
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.9
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.8
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.7
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.6
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.5
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.4
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.3
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.2
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.66.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.65.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.63.4
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.63.3
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.63.2
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.63.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.63.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.62.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.62.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.60.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.59.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.55.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.54.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.54.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.53.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.52.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.51.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.50.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.49.1
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.49.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.48.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.47.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.46.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.45.0
2 findingsMaintainer email '[email protected]' uses domain 'hejny.org' 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.