@balena/odata-to-abstract-sql
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 | slsa-provenance | AI (provenance): Balena org uses GitHub Actions CI/CD with SLSA attestation; stable publishing pattern going forward. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by migration to GitHub Actions publishing; SLSA attestation confirms legitimate CI origin. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from balena.io account to GitHub Actions is a documented CI/CD migration pattern for this org; SLSA attestation corroborates legitimacy. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): @types/lodash is a TypeScript type declaration package; declared in dependencies for consumers, not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/memoizee | AI (phantom-deps): @types/memoizee is a TypeScript type declaration package; declared in dependencies for consumers, not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/string-hash | AI (phantom-deps): @types/string-hash is a TypeScript type declaration package; declared in dependencies for consumers, not directly imported. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 10.0.22 | 8 / 16 | |
| 10.0.21 | 8 / 16 | |
| 10.0.20 | 8 / 16 | |
| 10.0.19 | 8 / 16 | |
| 10.0.18 | 8 / 16 | |
| 10.0.17 | 8 / 16 | |
| 10.0.16 | 8 / 16 | |
| 10.0.15 | 8 / 16 | |
| 10.0.14 | 8 / 16 | |
| 10.0.13 | 8 / 16 | |
| 10.0.12 | 8 / 16 | |
| 10.0.11 | 8 / 16 | |
| 10.0.10 | 8 / 16 | |
| 10.0.9 | 8 / 16 | |
| 10.0.8 | 8 / 16 | |
| 10.0.7 | 8 / 16 | |
| 10.0.6 | 8 / 16 | |
| 10.0.5 | 8 / 16 | |
| 10.0.4 | 8 / 16 | |
| 10.0.3 | 8 / 16 | |
| 10.0.2 | 8 / 16 | |
| 10.0.1 | 8 / 16 | |
| 10.0.0 | 8 / 16 |
v10.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.8
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.