@lumenflow/packs-software-delivery
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Major version bump with significant feature expansion; 136 new files consistent with scope growth. | ai | |
| source-diff | source-size-tripled | AI (source-diff): v4→v5 major release; size increase matches new modules (sandbox, policy, config, domain, methodology). | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): Deps referenced in config/tooling context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): Deps referenced in config/tooling context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:p-retry | AI (phantom-deps): Deps referenced in config/tooling context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:gray-matter | AI (phantom-deps): Deps referenced in config/tooling context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Deps referenced in config/tooling context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Deps referenced in config/tooling context; stable false positive for this package. | ai |
Versions (showing 16 of 116)
| Version | Deps | Published |
|---|---|---|
| 3.9.8 | 1 / 3 | |
| 3.9.7 | 1 / 3 | |
| 3.9.6 | 1 / 3 | |
| 3.9.5 | 1 / 3 | |
| 3.9.2 | 1 / 3 | |
| 3.9.1 | 1 / 3 | |
| 3.9.0 | 1 / 3 | |
| 3.8.7 | 1 / 3 | |
| 3.8.6 | 1 / 3 | |
| 3.8.5 | 1 / 3 | |
| 3.8.4 | 1 / 3 | |
| 3.8.3 | 1 / 3 | |
| 3.8.2 | 1 / 3 | |
| 3.8.1 | 1 / 3 | |
| 3.8.0 | 1 / 3 | |
| 3.7.1 | 1 / 3 |
v3.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.