@basis-theory/basis-theory-js
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; reflects CI/CD migration for this org-owned package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 190 versions over 1768 days; gap reflects CI pipeline transition, not account takeover. | ai | |
| phantom-deps | phantom-dep:os-browserify | AI (phantom-deps): os-browserify is declared in package.json dependencies and referenced in config; stable false positive for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 4.30.2 | 7 / 0 | |
| 4.30.1 | 7 / 0 | |
| 4.30.0 | 7 / 0 | |
| 4.29.0 | 7 / 0 | |
| 4.28.2 | 7 / 0 | |
| 4.28.1 | 7 / 0 | |
| 4.28.0 | 7 / 0 | |
| 4.27.2 | 7 / 0 | |
| 4.27.1 | 7 / 0 | |
| 4.27.0 | 7 / 0 | |
| 4.26.0 | 7 / 0 | |
| 4.25.0 | 7 / 0 | |
| 4.24.1 | 7 / 0 | |
| 4.24.0 | 7 / 0 | |
| 4.23.1 | 7 / 0 | |
| 4.23.0 | 7 / 0 | |
| 4.22.1 | 7 / 0 | |
| 4.22.0 | 7 / 0 | |
| 4.21.2 | 8 / 0 | |
| 4.21.1 | 8 / 0 | |
| 4.21.0 | 8 / 0 | |
| 4.20.0 | 8 / 0 | |
| 4.19.0 | 7 / 0 | |
| 4.18.0 | 7 / 0 | |
| 4.17.1 | 7 / 0 | |
| 4.17.0 | 7 / 0 | |
| 4.16.0 | 7 / 0 | |
| 4.15.0 | 7 / 0 | |
| 4.14.0 | 7 / 0 | |
| 4.13.0 | 7 / 0 | |
| 4.12.0 | 7 / 0 | |
| 4.11.0 | 7 / 0 | |
| 4.10.1 | 7 / 0 | |
| 4.10.0 | 7 / 0 | |
| 4.9.0 | 7 / 0 | |
| 4.8.0 | 7 / 0 | |
| 4.7.2 | 7 / 0 | |
| 4.7.1 | 7 / 0 | |
| 4.7.0 | 7 / 0 | |
| 4.6.2 | 7 / 0 | |
| 4.6.1 | 7 / 0 | |
| 4.6.0 | 7 / 0 | |
| 4.5.0 | 7 / 0 |
v4.30.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matthew_basistheory) than the most recent previously approved version (bt-platform) on 2024-10-31, but matthew_basistheory 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.
v4.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matthew_basistheory) than the most recent previously approved version (bt-platform) on 2024-10-29, but matthew_basistheory 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.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.