is2
A type checking library where each exported function returns either true or false and does not throw. Also added tests.
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:stdarg.com | AI (email-domain): Long-lived package (4813 days) with 30 versions; unclaimed domain is a pre-existing background risk, not a new threat introduced in this or any recent version. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package (4813 days old); lack of provenance attestation is expected for packages predating Sigstore and is not a meaningful risk signal here. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ip-regex is a well-known package and directly relevant to is2's network/IP type-checking functionality. Addition is legitimate and expected. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.0.9 | 3 / 2 | |
| 2.0.8 | 3 / 2 | |
| 2.0.7 | 3 / 2 | |
| 2.0.6 | 3 / 2 | |
| 2.0.4 | 3 / 2 | |
| 2.0.1 | 3 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.0.9 | 2 / 3 | |
| 1.0.8 | 2 / 3 | |
| 1.0.7 | 3 / 3 | |
| 1.0.6 | 3 / 3 | |
| 1.0.5 | 3 / 3 | |
| 1.0.4 | 3 / 3 | |
| 1.0.3 | 2 / 3 | |
| 1.0.2 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 | |
| 0.0.13 | 1 / 2 | |
| 0.0.12 | 1 / 2 | |
| 0.0.11 | 1 / 2 | |
| 0.0.10 | 1 / 2 | |
| 0.0.9 | 1 / 2 | |
| 0.0.8 | 1 / 2 | |
| 0.0.7 | 0 / 2 | |
| 0.0.6 | 0 / 2 | |
| 0.0.5 | 0 / 2 | |
| 0.0.4 | 0 / 2 | |
| 0.0.3 | 0 / 2 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 0 / 2 |
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
2 findingsMaintainer email '[email protected]' uses domain 'stdarg.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
2 findingsMaintainer email '[email protected]' uses domain 'stdarg.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.
v2.0.4
2 findingsMaintainer email '[email protected]' uses domain 'stdarg.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.
v2.0.1
2 findingsMaintainer email '[email protected]' uses domain 'stdarg.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.
v2.0.0
2 findingsMaintainer email '[email protected]' uses domain 'stdarg.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.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.