pjs
A lightweight class system. It's just prototypes!
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 |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): The install script runs 'make commonjs', a local build step to compile CommonJS output. No network access or arbitrary code execution; stable pattern for this package across versions. | ai | |
| provenance | no-provenance | AI (provenance): Mature package (5224 days old) with strong publisher track record; lack of provenance is expected for older packages and not a meaningful risk signal here. | ai | |
| email-domain | unclaimed-email:jjmadkisson at gmail dot com | AI (email-domain): Gmail.com is a Google-hosted domain and cannot be hijacked. This is a false positive — the rule appears to have misidentified the gmail.com domain as unclaimed. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Version diff shows no material changes; dormancy followed by a clean maintenance release on a 14-year-old package with strong publisher history is not indicative of takeover. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.1.2 | 0 / 2 | |
| 5.1.1 | 0 / 2 | |
| 5.1.0 | 0 / 2 | |
| 5.0.0 | 0 / 2 | |
| 4.0.0 | 0 / 2 | |
| 3.1.0 | 0 / 2 | |
| 3.0.2 | 0 / 2 | |
| 3.0.0 | 0 / 2 | |
| 2.0.2 | 0 / 2 | |
| 2.0.1 | 0 / 2 | |
| 2.0.0 | 0 / 3 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.3 | 0 / 2 | |
| 0.1.2 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 1 | |
| 0.0.3 | 0 / 1 | |
| 0.0.2 | 0 / 1 |
v5.1.2
2 findingsMaintainer email 'jneen at jneen dot net' uses domain 'jneen at jneen dot net' 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.
v5.1.1
2 findingsMaintainer email 'jneen at jneen dot net' uses domain 'jneen at jneen dot net' 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.
v5.1.0
2 findingsMaintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' 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.
v5.0.0
3 findingsScript: make commonjs
Maintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' 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.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.