@marcfargas/odoo-testcontainers
Testcontainers module for Odoo development
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA attestation — documented CI/CD publishing transition for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): debug and dockerode are established packages that match the package's Docker/testcontainers functionality. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of dockerode runtime dependency and its type definitions. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI with Sigstore attestation; stable positive signal across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.5 | 5 / 5 | |
| 0.1.4 | 5 / 5 | |
| 0.1.3 | 5 / 5 | |
| 0.1.2 | 4 / 4 | |
| 0.1.0 | 3 / 3 |
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
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.
v0.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-14. 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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.