@promptbook/anthropic-claude
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:hejny.org | AI (email-domain): Longstanding publisher identity across 800+ versions; no hijack evidence. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): spacetrim is the author's own established utility, used across promptbook packages. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard Proxy trap implementation using Reflect.get/has; not obfuscation, stable pattern across this package's versions. | ai |
Versions (showing 69 of 69)
| Version | Deps | Published |
|---|---|---|
| 0.112.0 | 6 / 0 | |
| 0.110.0 | 6 / 0 | |
| 0.105.0 | 6 / 0 | |
| 0.104.0 | 6 / 0 | |
| 0.103.0 | 6 / 0 | |
| 0.102.0 | 6 / 0 | |
| 0.101.0 | 6 / 0 | |
| 0.100.2 | 6 / 0 | |
| 0.100.1 | 6 / 0 | |
| 0.100.0 | 6 / 0 | |
| 0.98.0 | 6 / 0 | |
| 0.95.0 | 6 / 0 | |
| 0.94.0 | 6 / 0 | |
| 0.93.0 | 6 / 0 | |
| 0.92.0 | 6 / 0 | |
| 0.89.0 | 5 / 0 | |
| 0.88.0 | 5 / 0 | |
| 0.86.31 | 4 / 0 | |
| 0.86.30 | 4 / 0 | |
| 0.86.22 | 4 / 0 | |
| 0.86.10 | 4 / 0 | |
| 0.86.8 | 4 / 0 | |
| 0.86.6 | 4 / 0 | |
| 0.86.5 | 4 / 0 | |
| 0.85.0 | 4 / 0 | |
| 0.84.0 | 4 / 0 | |
| 0.83.0 | 4 / 0 | |
| 0.82.0 | 4 / 0 | |
| 0.81.0 | 4 / 0 | |
| 0.80.0 | 4 / 0 | |
| 0.79.0 | 4 / 0 | |
| 0.78.4 | 4 / 0 | |
| 0.78.3 | 4 / 0 | |
| 0.78.2 | 4 / 0 | |
| 0.77.1 | 4 / 0 | |
| 0.77.0 | 4 / 0 | |
| 0.76.0 | 4 / 0 | |
| 0.75.10 | 4 / 0 | |
| 0.75.9 | 4 / 0 | |
| 0.75.8 | 4 / 0 | |
| 0.75.6 | 4 / 0 | |
| 0.75.5 | 4 / 0 | |
| 0.75.4 | 4 / 0 | |
| 0.75.3 | 4 / 0 | |
| 0.75.2 | 4 / 0 | |
| 0.75.1 | 4 / 0 | |
| 0.74.0 | 4 / 0 | |
| 0.73.0 | 4 / 0 | |
| 0.72.0 | 4 / 0 | |
| 0.69.6 | 4 / 0 | |
| 0.69.1 | 4 / 0 | |
| 0.69.0 | 4 / 0 | |
| 0.68.5 | 4 / 0 | |
| 0.67.9 | 4 / 0 | |
| 0.67.5 | 4 / 0 | |
| 0.67.0 | 4 / 0 | |
| 0.66.0 | 4 / 0 | |
| 0.63.2 | 3 / 0 | |
| 0.59.0 | 3 / 0 | |
| 0.58.0 | 2 / 0 | |
| 0.57.2 | 2 / 0 | |
| 0.57.1 | 2 / 0 | |
| 0.57.0 | 2 / 0 | |
| 0.56.0 | 2 / 0 | |
| 0.55.0 | 2 / 0 | |
| 0.54.1 | 2 / 0 | |
| 0.54.0 | 2 / 0 | |
| 0.53.0 | 2 / 0 | |
| 0.52.0 | 2 / 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.8
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.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.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.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.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.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.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.