@dofe/infra-shared-services
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dofe/infra-rabbitmq | AI (dependencies): Internal @dofe org dependency; consistent pattern across all @dofe/infra-* packages in this ecosystem. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo with coordinated releases across @dofe/* packages; rapid successive publishes are expected. | ai | |
| provenance | no-provenance | AI (provenance): Internal monorepo package; provenance not configured for this org's publishing workflow. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package under @dofe/ scope; missing metadata is typical for private infra libs published publicly. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal infra package; missing description is consistent across the @dofe/ org packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.1.38 | 7 / 2 | |
| 0.1.37 | 7 / 2 | |
| 0.1.36 | 7 / 2 | |
| 0.1.35 | 7 / 2 | |
| 0.1.33 | 7 / 2 | |
| 0.1.32 | 7 / 2 | |
| 0.1.31 | 7 / 2 | |
| 0.1.29 | 7 / 2 | |
| 0.1.28 | 7 / 2 | |
| 0.1.22 | 7 / 2 | |
| 0.1.20 | 7 / 2 | |
| 0.1.18 | 6 / 2 | |
| 0.1.17 | 6 / 2 | |
| 0.1.14 | 6 / 2 | |
| 0.1.12 | 6 / 2 | |
| 0.1.9 | 6 / 2 | |
| 0.1.6 | 6 / 2 | |
| 0.1.5 | 6 / 2 | |
| 0.1.2 | 6 / 2 | |
| 0.1.1 | 6 / 2 |
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.