@honeybadger-io/js
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @honeybadger-io/js; Levenshtein match to 'qs' is a false positive from comparing a long scoped name. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Same false-positive pattern; no relation to jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same false-positive pattern; no relation to pg. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Same false-positive pattern; no relation to rxjs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same false-positive pattern; no relation to joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same false-positive pattern; no relation to ajv. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a type-only dep used for TypeScript declarations, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): @types/aws-lambda is a type-only dep used for TypeScript declarations, not directly imported at runtime. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 6.15.3 | 3 / 21 | |
| 6.15.2 | 3 / 19 | |
| 6.15.0 | 3 / 19 | |
| 6.12.3 | 3 / 19 | |
| 6.12.2 | 3 / 19 | |
| 6.12.1 | 3 / 19 | |
| 6.12.0 | 3 / 19 | |
| 6.11.3 | 3 / 19 | |
| 6.11.2 | 3 / 19 | |
| 6.11.1 | 3 / 19 | |
| 6.11.0 | 3 / 19 | |
| 6.10.1 | 3 / 19 | |
| 6.10.0 | 3 / 19 | |
| 6.9.3 | 3 / 18 | |
| 6.9.2 | 3 / 19 | |
| 6.9.1 | 3 / 19 | |
| 6.9.0 | 3 / 19 | |
| 6.8.3 | 3 / 19 | |
| 6.8.2 | 4 / 19 | |
| 6.8.1 | 4 / 19 | |
| 6.8.0 | 4 / 19 | |
| 6.7.2 | 4 / 19 | |
| 6.7.1 | 4 / 19 | |
| 6.7.0 | 4 / 19 | |
| 6.6.1 | 4 / 19 | |
| 6.6.0 | 4 / 19 | |
| 6.5.3 | 3 / 18 | |
| 6.5.2 | 3 / 18 | |
| 6.5.1 | 3 / 18 | |
| 6.5.0 | 3 / 16 | |
| 6.4.3 | 3 / 16 | |
| 6.4.2 | 3 / 16 | |
| 6.4.1 | 3 / 16 | |
| 6.4.0 | 3 / 16 | |
| 6.3.0 | 3 / 16 | |
| 6.2.0 | 3 / 16 | |
| 6.1.3 | 3 / 16 | |
| 6.1.2 | 3 / 16 | |
| 6.1.1 | 3 / 16 | |
| 6.1.0 | 3 / 16 | |
| 6.0.0 | 3 / 16 |
v6.15.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (subzero10) on 2026-07-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v6.15.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (subzero10) on unknown date, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v6.15.0
2 findingsThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.
This version was published by a different npm account (subzero10) than the most recent previously approved version (GitHub Actions) on 2026-07-17, but subzero10 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.