@bemedev/dev-utils
A collection of utilities for Node.js development, including build tools, testing utilities, and configuration management.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:rollup-plugin-tsc-alias | AI (dependencies): Legitimate rollup plugin for TSC alias resolution; appropriate for a dev-utils build tooling package. | ai | |
| dependencies | unvetted-dep:rollup-plugin-circular-dependencies | AI (dependencies): Legitimate rollup plugin for circular dependency detection; appropriate for a dev-utils build tooling package. | ai | |
| provenance | publisher-changed | AI (provenance): GitHub Actions publisher is backed by SLSA Sigstore attestation; legitimate CI/CD transition for this package. | ai | |
| provenance | no-provenance | AI (provenance): Small dev-utils package; lack of provenance is common and no other risk signals present. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 10 / 24 | |
| 0.6.11 | 10 / 24 | |
| 0.6.10 | 10 / 24 | |
| 0.6.9 | 10 / 24 | |
| 0.6.8 | 10 / 24 | |
| 0.6.7 | 10 / 24 | |
| 0.6.6 | 10 / 24 | |
| 0.6.5 | 10 / 24 | |
| 0.6.4 | 10 / 27 | |
| 0.6.3 | 10 / 27 | |
| 0.6.2 | 10 / 27 | |
| 0.6.1 | 10 / 26 | |
| 0.6.0 | 10 / 26 | |
| 0.5.3 | 10 / 26 | |
| 0.5.2 | 10 / 26 | |
| 0.5.1 | 10 / 26 | |
| 0.5.0 | 10 / 26 | |
| 0.4.0 | 10 / 26 | |
| 0.3.2 | 10 / 26 | |
| 0.3.1 | 10 / 26 | |
| 0.1.2 | 10 / 26 | |
| 0.1.1 | 10 / 30 | |
| 0.1.0 | 10 / 30 |
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. 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.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.