@beautinique/be-middlewares
Middlewares for the Beautinique backend project.
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:@beautinique/be-utils | AI (dependencies): First-party sibling package from same publisher; consistent pattern across the @beautinique scope. | ai | |
| dependencies | unvetted-dep:@beautinique/be-classes | AI (dependencies): First-party sibling package from same publisher; consistent pattern across the @beautinique scope. | ai | |
| dependencies | unvetted-dep:@beautinique/be-constants | AI (dependencies): First-party sibling package from same publisher; consistent pattern across the @beautinique scope. | ai | |
| provenance | no-provenance | AI (provenance): New org package; absence of provenance is common and not a risk signal here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.20 | 6 / 9 | |
| 1.0.19 | 6 / 9 | |
| 1.0.18 | 6 / 9 | |
| 1.0.17 | 6 / 9 | |
| 1.0.16 | 6 / 9 | |
| 1.0.15 | 6 / 9 | |
| 1.0.14 | 6 / 9 | |
| 1.0.13 | 6 / 9 | |
| 1.0.9 | 6 / 9 | |
| 1.0.8 | 6 / 9 | |
| 1.0.7 | 7 / 8 | |
| 1.0.6 | 7 / 8 | |
| 1.0.1 | 7 / 8 | |
| 1.0.0 | 2 / 2 |
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.