@spectrum-web-components/meter
An `<sp-meter>` is a visual representation of a quantity or achievement. The meter's progress is determined by user actions, rather than system actions.
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): rubenc is a trusted Adobe org publisher with 684 approved packages; transition appears to be a legitimate maintainer rotation within the org. | ai | |
| provenance | no-provenance | AI (provenance): Adobe's spectrum-web-components monorepo does not publish with Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Sibling dep from same Adobe monorepo; unvetted status is a pipeline gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/shared | AI (dependencies): Sibling dep from same Adobe monorepo; unvetted status is a pipeline gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/field-label | AI (dependencies): Sibling dep from same Adobe monorepo; unvetted status is a pipeline gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Sibling dep from same Adobe monorepo; unvetted status is a pipeline gap, not a risk signal. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 4 / 0 | |
| 1.12.0 | 4 / 0 | |
| 1.11.2 | 4 / 0 | |
| 1.11.1 | 4 / 0 | |
| 1.11.0 | 4 / 0 | |
| 1.10.0 | 4 / 0 | |
| 1.9.1 | 4 / 0 | |
| 1.9.0 | 4 / 0 | |
| 1.8.0 | 4 / 0 | |
| 1.7.0 | 4 / 0 | |
| 1.6.0 | 4 / 2 |
v1.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.