@powerlines/plugin-id
A Powerlines plugin that provides unique identifier generation capabilities at runtime by adding the `id` builtin module.
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): Storm Software transitioned to GitHub Actions CI/CD publishing; SLSA provenance attestation confirms integrity. This is a stable organizational publishing pattern, not a compromise. | ai | |
| phantom-deps | phantom-dep:defu | AI (phantom-deps): defu is a declared dependency used in config files; phantom detection is a false positive for this plugin package's build/config pattern. | ai | |
| phantom-deps | phantom-dep:powerlines | AI (phantom-deps): powerlines is a declared peer/runtime dependency for this plugin package; not directly imported in source but used at runtime. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@stryke/path | AI (phantom-deps): Declared for config/build-time use in a monorepo tooling context; not a security concern for this Storm Software ecosystem package. | ai | |
| phantom-deps | phantom-dep:@storm-software/config-tools | AI (phantom-deps): Declared for config/build-time use in a monorepo tooling context; not a security concern for this Storm Software ecosystem package. | ai |
Versions (showing 100 of 588)
| Version | Deps | Published |
|---|---|---|
| 0.9.483 | 4 / 2 | |
| 0.9.482 | 4 / 2 | |
| 0.9.481 | 4 / 2 | |
| 0.9.480 | 4 / 2 | |
| 0.9.479 | 4 / 2 | |
| 0.9.478 | 4 / 2 | |
| 0.9.477 | 4 / 2 | |
| 0.9.474 | 4 / 2 | |
| 0.9.473 | 4 / 2 | |
| 0.9.472 | 4 / 2 | |
| 0.9.471 | 4 / 2 | |
| 0.9.470 | 4 / 2 | |
| 0.9.468 | 4 / 2 | |
| 0.9.467 | 4 / 2 | |
| 0.9.466 | 4 / 2 | |
| 0.9.465 | 4 / 2 | |
| 0.9.464 | 4 / 2 | |
| 0.9.463 | 4 / 2 | |
| 0.9.462 | 4 / 2 | |
| 0.9.461 | 4 / 2 | |
| 0.9.460 | 4 / 2 | |
| 0.9.459 | 4 / 2 | |
| 0.9.458 | 4 / 2 | |
| 0.9.457 | 4 / 2 | |
| 0.9.456 | 4 / 2 | |
| 0.9.455 | 4 / 2 | |
| 0.9.454 | 4 / 2 | |
| 0.9.453 | 4 / 2 | |
| 0.9.452 | 4 / 2 | |
| 0.9.451 | 4 / 2 | |
| 0.9.450 | 4 / 2 | |
| 0.9.449 | 4 / 2 | |
| 0.9.448 | 4 / 2 | |
| 0.9.447 | 4 / 2 | |
| 0.9.446 | 4 / 2 | |
| 0.9.445 | 4 / 2 | |
| 0.9.444 | 4 / 2 | |
| 0.9.443 | 4 / 2 | |
| 0.9.441 | 4 / 2 | |
| 0.9.440 | 4 / 2 | |
| 0.9.439 | 4 / 2 | |
| 0.9.438 | 4 / 2 | |
| 0.9.437 | 4 / 2 | |
| 0.9.436 | 4 / 2 | |
| 0.9.435 | 4 / 2 | |
| 0.9.434 | 4 / 2 | |
| 0.9.433 | 4 / 2 | |
| 0.9.432 | 4 / 2 | |
| 0.9.431 | 4 / 2 | |
| 0.9.430 | 4 / 2 | |
| 0.9.429 | 4 / 2 | |
| 0.9.428 | 4 / 2 | |
| 0.9.427 | 4 / 2 | |
| 0.9.426 | 4 / 2 | |
| 0.9.425 | 4 / 2 | |
| 0.9.424 | 4 / 2 | |
| 0.9.423 | 4 / 2 | |
| 0.9.422 | 4 / 2 | |
| 0.9.421 | 4 / 2 | |
| 0.9.420 | 4 / 2 | |
| 0.9.419 | 4 / 2 | |
| 0.9.418 | 4 / 2 | |
| 0.9.417 | 4 / 2 | |
| 0.9.415 | 4 / 2 | |
| 0.9.414 | 4 / 2 | |
| 0.9.413 | 4 / 2 | |
| 0.9.412 | 4 / 2 | |
| 0.9.411 | 4 / 2 | |
| 0.9.410 | 4 / 2 | |
| 0.9.409 | 4 / 2 | |
| 0.9.408 | 4 / 2 | |
| 0.9.407 | 4 / 2 | |
| 0.9.406 | 4 / 2 | |
| 0.9.405 | 4 / 2 | |
| 0.9.404 | 4 / 2 | |
| 0.9.403 | 4 / 2 | |
| 0.9.402 | 4 / 2 | |
| 0.9.401 | 4 / 2 | |
| 0.9.400 | 4 / 2 | |
| 0.9.399 | 4 / 2 | |
| 0.9.398 | 4 / 2 | |
| 0.9.397 | 4 / 2 | |
| 0.9.396 | 4 / 2 | |
| 0.9.395 | 4 / 2 | |
| 0.9.394 | 4 / 2 | |
| 0.9.393 | 4 / 2 | |
| 0.9.392 | 4 / 2 | |
| 0.9.391 | 4 / 2 | |
| 0.9.390 | 4 / 2 | |
| 0.9.389 | 4 / 2 | |
| 0.9.388 | 4 / 2 | |
| 0.9.387 | 4 / 2 | |
| 0.9.386 | 4 / 2 | |
| 0.9.385 | 4 / 2 | |
| 0.9.384 | 4 / 2 | |
| 0.9.383 | 4 / 2 | |
| 0.9.382 | 4 / 2 | |
| 0.9.381 | 4 / 2 | |
| 0.9.380 | 4 / 2 | |
| 0.9.379 | 4 / 2 |
v0.9.483
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.482
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.481
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.480
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.479
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.478
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.477
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.474
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.473
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.472
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.471
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.470
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.468
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.467
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.466
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.465
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.464
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.463
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.462
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.461
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.460
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.459
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.458
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.387
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.9.386
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.9.385
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.9.384
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.9.383
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. 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.9.382
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. 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.9.381
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. 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.9.380
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. 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.9.379
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. 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.